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
- 299
- Versions published
- 13
- First published
- May 2026
- Publisher
- nearlcrews
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
Scripts17
buildnpm run clean && npm run build:types && npm run build:bundle && npm run build:panelbuild:bundlenode esbuild.config.mjsbuild:panelwebpack --config webpack.config.cjsbuild:typestsc --emitDeclarationOnly --declaration --outDir distcleannode -e "const fs=require('node:fs');for(const d of ['dist','public'])fs.rmSync(d,{recursive:true,force:true})"devtsx watch src/index.tsformatbiome format --write src/ tests/lintbiome check src/ tests/lint:fixbiome check --write src/ tests/prepublishOnlynpm run type-check && npm run lint && npm run test && npm run buildsecurity-auditnpm audit --audit-level=moderatetestvitest runtest:coveragevitest run --coveragetest:runvitest runtest:watchvitesttype-checktsc --noEmit && tsc -p tsconfig.tests.json && tsc -p tsconfig.panel.jsonvalidatenpm run type-check && npm run lint && npm run test:run
Dependencies1
croner^10.0.1