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
- 9
- First published
- May 2026
- Publisher
- samdevlabs
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
Scripts3
build:jsbabel src --out-dir dist --copy-filesstartnode index.jstestecho "Error: no test specified" && exit 1
Dependencies18
@babel/runtime^7.29.7axios^1.16.1body-parser^2.2.2cookie-parser^1.4.7debug^4.4.3dotenv^17.4.2express^5.2.1fast-url-parser^1.1.3form-data^4.0.5got^14.6.6helmet^8.2.0jsonwebtoken^9.0.3nodemon^3.1.14pg^8.21.0pg-hstore^2.3.4rasha^1.2.5sequelize^6.37.8sprightly^2.0.1