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.
- Versions published
- 18
- First published
- Mar 2026
- Publisher
- dickolsson
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":["@forwardimpact/[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":["@forwardimpact/[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
Scripts3
devnode --watch server.jsstartbunx download && bun server.jstestbun test test/*.test.js
Dependencies10
@forwardimpact/libconfig^0.1.58@forwardimpact/libpreflight^0.1.0@forwardimpact/libproto^0.1.0@forwardimpact/libresource^0.1.89@forwardimpact/librpc^0.1.77@forwardimpact/libstorage^0.1.53@forwardimpact/libtelemetry^0.1.41@forwardimpact/libtype^0.1.63@forwardimpact/libutil^0.1.85@forwardimpact/libvector^0.1.68