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
- 582
- Versions published
- 27Established · −30% score
- First published
- Oct 2025
- Publisher
- nearlcrews
Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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":["[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":["[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
Scripts23
buildnpm run clean && npm run build:types && npm run build:bundle && npm run build:panelbuild:bundlenode esbuild.config.jsbuild:panelwebpackbuild:typestsc --noEmit false --declaration --emitDeclarationOnly --outDir distcleannode scripts/clean.mjscreate-releasegh release create v$npm_package_version --generate-notesdevtsx watch src/index.tsformatbiome format --write .hookshuskylintbiome check .lint:fixbiome check --write .mutation-teststryker runprepacknpm run buildprepublishOnlynpm run validate && npm run buildreleasegit rev-parse "v$npm_package_version" >/dev/null 2>&1 && { echo "tag v$npm_package_version already exists"; exit 1; } ; git tag v$npm_package_version && git push --tags && git push && npm run create-releasesecurity-auditnpm audit --audit-level=moderatetestvitest runtest:coveragevitest run --coveragetest:runvitest runtest:uivitest --uitest:watchvitesttype-checktsc --noEmitvalidatenpm run type-check && npm run lint && npm run test:run