@osm-conflation-engine/cli@3.12.0
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s OSM processing and authentication flows appear consistent with its purpose, but a normal run in GitHub Actions also sends the complete configuration to the package service without an evident telemetry opt-in. Because that configuration can disclose repository or local path information, this is suspicious runtime telemetry rather than clear malicious credential theft.
Decision evidence
public snapshot- A normal run calls the run-history updater after generating its result.
- In GitHub Actions, the updater requests an OIDC token and sends the result to the package’s service.
- The result includes the complete config, warnings, and aggregate run counts.
- The config schema includes a source data file path, which can disclose a local or repository path.
- The package declares no install or postinstall hook; its manifest exports library entrypoints.
- The upload is gated on GITHUB_ACTIONS and uses a token scoped to the package service.
- OSM_AUTH is used in the PBF download flow to authenticate with OpenStreetMap and Geofabrik.
Source & flagged code
5 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @osm-conflation-engine/cli@3.12.0.
See all versions of @osm-conflation-engine/cli for other recorded verdicts.
- Review the evidence and your use of @osm-conflation-engine/cli@3.12.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.