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
- 531
- Versions published
- 127Mature · −50% score
- First published
- Dec 2019
- Publisher
- spica-bot
Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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":["@spica/[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":["@spica/[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
Dependencies25
@caporal/core^2.0.7@nestjs/common10.4.22@nx/devkit20.8.4@types/dockerode3.3.47@types/semver7.7.1axios^1.8.2chokidar^4.0.3colorette^2.0.20columnify^1.6.0cosmiconfig^9.0.0diff4.0.4dockerode^4.0.4dotenv^16.4.7get-port^7.1.0json-schema0.4.0jsonpath^1.1.1lodash4.18.1mongodb6.21.0open^10.1.0ora^8.2.0pretty-ms^9.2.0rxjs7.8.2semver^7.7.1typescript^5.7.3yaml^2.7.1