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
- 2
- First published
- Aug 2024
- Publisher
- marzab
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":["@povio/[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":["@povio/[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
Scripts7
buildtsupcliDEBUG_COLORS=1 DEBUG='scaffold:*' node -r @swc-node/register src/sh.tslintbiome check --write .lint:checkbiome checkpushyarn exec ./scripts/publish.shtestDEBUG_COLORS=1 DEBUG='scaffold:*' node --test -r @swc-node/register src/**/*.test.tstest:watchDEBUG_COLORS=1 DEBUG='scaffold:*' node --test --watch -r @swc-node/register src/**/*.test.ts
Dependencies10
colorette^2.0.20debug^4.4.3fast-glob^3.3.3interpret^3.1.1lodash^4.17.21rechoir^0.8.0semver^7.7.3ts-morph^27.0.0yaml^2.8.1zod^4.1.12