@osm-conflation-engine/cli@3.1.0
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe flagged network, environment, and subprocess primitives implement an explicit OSM conflation download workflow, not install-time or covert behavior. The configurable PBF URL cookie forwarding is a design risk for untrusted configurations, but source inspection does not establish malicious package behavior.
Decision evidence
public snapshot- `dist/index.mjs.map` contains user-invoked OSM_AUTH login and passes the resulting cookie to the configured PBF URL.
- `dist/index.mjs.map` spawns `curl`, but with a fixed executable and argument array rather than a shell.
- `package.json` has no preinstall, install, postinstall, or other lifecycle hook.
- `package.json` exposes a library entrypoint and declares no `bin` executable.
- `dist/index.mjs.map` shows all network activity occurs only inside exported `run()` download processing.
- `dist/index.mjs.map` writes intermediates beneath a deterministic subdirectory of the system temp directory.
- No eval/vm/dynamic loading, persistence, destructive system actions, or AI-agent control-surface paths were found.
- Known fetches target OSM, Geofabrik, Overpass, and the package-aligned ignore-list API.
Source & flagged code
4 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.1.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.1.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.