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
- 893
- Versions published
- 3
- First published
- Jan 2022
- Publisher
- dev.infra
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":["@aptos-scp/[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":["@aptos-scp/[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
Scripts9
buildnpm run build:cibuild:citsc && npm run lintclean:node_modulesrimraf 'node_modules'commitgit-czlinteslint -c .eslintrc.js --ext .ts "@(src|test)/**/*.ts?(x)"next-version./node_modules/@aptos-scp/scp-component-commit-configs/next-version.shreleasenpx semantic-releasetestnpm run build && npm run test:citest:ciLOG_LEVEL=ALL nyc mocha --reporter mocha-junit-reporter --reporter-options mochaFile=./reports/test-results.xml --exit