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
- 3
- First published
- May 2018
- Publisher
- smollweide
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":["@namics/[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":["@namics/[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
Scripts2
husky:pre-commitlint-stagedprettierprettier --write '**/*.*(js|jsx|ts|tsx|json)'
Dependencies21
autoprefixer8.5.0babel-core6.26.3babel-eslint8.2.3babel-loader7.1.4babel-preset-env1.7.0babel-runtime6.26.0cache-loader1.2.2case-sensitive-paths-webpack-plugin2.1.2css-loader0.28.11extract-text-webpack-plugin4.0.0-beta.0fork-ts-checker-webpack-plugin0.4.1html-webpack-plugin3.2.0iconfont-webpack-plugin2.0.0node-sass4.9.0postcss-loader2.1.5sass-loader7.0.1style-loader0.21.0thread-loader1.1.5ts-loader4.3.0typescript2.8.3webpack4.8.3