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
- 7
- First published
- Jun 2022
- Publisher
- cezaraugusto
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
Scripts5
cleanrm -rf distcompiletsup-node ./module.ts --format cjs --dts --target=node18 --minifylinteslint "./**/*.ts*"testecho "Note: no test specified" && exit 0watchyarn compile --watch
Dependencies8
@babel/plugin-proposal-class-properties^7.16.7@babel/plugin-proposal-decorators^7.24.0@babel/plugin-syntax-dynamic-import^7.8.3@babel/preset-env^7.24.0@babel/preset-react^7.23.3@babel/preset-typescript^7.23.3babel-plugin-react-require^4.0.2babel-plugin-transform-react-remove-prop-types^0.4.24