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
- 2
- First published
- Feb 2018
- Publisher
- hardfist
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
Scripts6
buildNODE_ENV=production webpack --progress -p --config scripts/config/webpack.config.prod.jsformatprettier-eslint --write public/**/*.jslintslint public/**/*.jslint:fixeslint --fix public/jsprecommitlint-stagedstartNODE_ENV=development webpack-dev-server --config scripts/config/webpack.config.dev.js
Dependencies10
@babel/types^7.0.0-beta.40@types/react^16.0.38@types/react-dom^16.0.4babel-loader^7.1.2classnames^2.2.5lint-staged^7.0.0omit.js^1.0.0react^16.2.0react-dom^16.2.0webpack-dev-server^2.11.1