@osm-conflation-engine/cli@3.5.1
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package automatically uploads configuration that can include a repository URL and local file path to its own service during GitHub Actions runs. This is undisclosed runtime telemetry carrying identifying details, so it warrants a warning rather than a publish block.
Decision evidence
public snapshot- After a conflate run, code in GitHub Actions obtains an OIDC token for osm-conflation-engine and sends a PUT request to the package service's run_history endpoint with JSON.stringify(e) as the body.
- The uploaded object includes the full config, warnings, and run counts.
- The config schema allows values such as a GitHub repository URL and a local source-data file path, so the upload can include identifying project details.
- The upload is limited to GitHub Actions and uses an OIDC token addressed to the package's own service.
- The manifest has no preinstall, install, or postinstall hook.
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.5.1.
See all versions of @osm-conflation-engine/cli for other recorded verdicts.
- Review the evidence and your use of @osm-conflation-engine/cli@3.5.1 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.