@osm-conflation-engine/cli@3.4.4
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package automatically posts project configuration and run details to its service from GitHub Actions, with no evident disclosure or opt-out. The OSM credential and download flows appear related to retrieving OSM data, so the identified issue is warning-level telemetry rather than credential theft or malicious execution.
Decision evidence
public snapshot- After conflate completes, the package calls its run-history updater.
- In GitHub Actions, the updater obtains an OIDC token and sends a PUT request to the package service.
- The request serializes the run object, which contains the user configuration, warnings, and run counts.
- The manifest exports a library entrypoint and declares no install lifecycle hook.
- The run-history request is limited to GitHub Actions and uses an OIDC token for the package service.
- The package’s OSM credential flow is used for OpenStreetMap access, and the curl process downloads the configured extract.
Source & flagged code
7 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @osm-conflation-engine/cli@3.4.4.
See all versions of @osm-conflation-engine/cli for other recorded verdicts.
- Review the evidence and your use of @osm-conflation-engine/cli@3.4.4 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.