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
- 1
- First published
- May 2021
- Publisher
- manycore_root
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":["@manycore/[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":["@manycore/[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
Scripts5
lint-stagedlint-stagedtest:allBABEL_ENV=test jest --detectOpenHandles --forceExit --verbose --coveragetest:clearBABEL_ENV=test jest --clearCachetest:debugBABEL_ENV=test node --inspect-brk node_modules/.bin/jest --runInBandtest:watchBABEL_ENV=test jest --watch --verbose --coverage
Dependencies11
@qunhe/cos-uploader^0.0.4@qunhe/log4js^0.0.7adm-zip^0.5.5axios^0.19.0form-data^4.0.0fs-extra^9.1.0lodash^4.17.21read-pkg-up7.0.0semver^7.3.5simple-git^2.38.0write-pkg^4.0.0