Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Weekly downloads
- 3
- Versions published
- 3
- First published
- Apr 2022
- Publisher
- caldwellc
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["@ngageoint/[email protected]"],"fail_on":"review"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["@ngageoint/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts6
cleanrm -rf ./.test_run; rm -rf ./.nyc_output; rm -rf ./docs/coverageclean-builtrm -rf ./builtpreparerm -rf ./built && npm run tscreportnyc reporttestnpm run clean-built && nyc mocha -r ts-node/registertscrm -rf ./built && tsc; cp ./node_modules/@ngageoint/geopackage/dist/canvaskit/canvaskit.wasm built/canvaskit.wasm
Dependencies8
@mapbox/vector-tile1.3.1@ngageoint/geopackage4.1.0@ngageoint/geopackage-geojson-js4.1.2@turf/intersect^3.7.5geojson-clip-polygon^1.0.3global-mercator^1.8.0jsts^1.3.0pbf^3.0.5