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
- 5
- First published
- May 2026
- Publisher
- ianmenethil
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":["@ianmenethil/[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":["@ianmenethil/[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
Scripts21
buildbun run check && bun run scripts/build.ts && bun run manifest && bun run validate:distbuild:types:v6bunx tsc -p tsconfig.build.jsonbuild:v6bun run scripts/build.ts --v6checkbun run lint && bun run typecheck && bun run jscpd && bunx knip --config knip.json && bun run test:v6jscpdbunx jscpd --config jscpd.jsonlintbunx eslint --config eslint.config.ts .lint:fixbunx eslint . --fixmanifestbun run scripts/generate-manifest.tsprepublishOnlybun run buildreleasesh -c 'V=$(npm version "${1:-minor}" -m "chore: release %s" | tail -1 | sed s/v//) && bun run build && npm publish --access public && mkdir -p "F:/_ZP-Main/apps/CDN-server/public/hcp/$V" && cp -r dist/cdn/* "F:/_ZP-Main/apps/CDN-server/public/hcp/$V/" && mkdir -p "F:/_ZP-Main/apps/CDN-server/public/hcp/latest" && cp -r dist/cdn/* "F:/_ZP-Main/apps/CDN-server/public/hcp/latest/" && git push --follow-tags' --release:majorbun run release majorrelease:minorbun run release minorrelease:patchbun run release patchtestbun run test:vitesttest:dombunx vitest run tests/dom --config vitest.config.tstest:e2eplaywright test --config tests/e2e/playwright.live.config.jstest:unitbunx vitest run tests/unit --config vitest.config.tstest:v6bunx vitest run tests/v6 --config vitest.config.ts --coverage --coverage.include='src/v6/**' --coverage.reportsDirectory=coverage/v6 --outputFile.json=reports/vitest/v6/results.json --outputFile.junit=reports/vitest/v6/junit.xml --outputFile.html=reports/vitest/v6/html/index.htmltest:vitestbunx vitest run tests/unit tests/dom tests/v6 --config vitest.config.tstypecheckbunx tsc -p tsconfig.json --noEmitvalidate:distbun run scripts/validate-dist.ts
Dependencies1
@noble/hashes^2.2.0