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
- 29
- Versions published
- 1
- First published
- Oct 2025
- Publisher
- snowden_
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":["@cainiaofe/[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":["@cainiaofe/[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
Scripts4
buildrm -rf lib && rm -rf es && tsc && tsc -p tsconfig.es.jsondevtsc -wprepublishOnlytnpm run buildpubnpm publish --registry=https://registry.npmjs.org --access=public && tnpm sync @cainiaofe/cone-core
Dependencies23
@babel/generator^7.17.7@babel/parser^7.20.15@babel/traverse^7.17.3@babel/types^7.17.0@koa/cors^4.0.0@koa/router^12.0.0axios^1.2.1chalk^4change-case^4.1.2ejs^3.1.8execa^5.1fs-extra^11.1.0koa^2.14.1koa-body^6.0.1koa-compose^4.1.0node-fetch^2npmlog^5.0.1open^6.4.0portfinder^1.0.32query-string^7semver^7.3.8type-fest^2typescript4.8.2