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
- 569
- Versions published
- 389Mature · −50% score
- First published
- Feb 2017
- Publisher
- tomprats
Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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
Remote Payload: matched "curl "
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 review · score 10 · status changed
Evidence
Static findings
3 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Payload | package/build/complete_external.sh | matched "curl " | 12 |
| medium | Remote Payload | package/build/create_order.sh | matched "curl " | 12 |
| medium | Remote Payload | package/build/get_external_id.sh | matched "curl " | 12 |
Manifest
Package metadata
Scripts21
buildnpm run build:lib && npm run build:compatibility -- --env output=standalonebuild:compatibilitywebpack --define-process-env-node-env production --env platform=browser --progressbuild:libwebpack --define-process-env-node-env production --progressdevwebpack serve --env platform=browserdev:securewebpack serve --env platform=browser --server-type httpsi18n-sync:testcd packages/i18n-sync && npm run test --i18n:synccd packages/i18n-sync && npm run i18n:sync --linteslint .lint:fixeslint . --fixprebuildmkdirp buildprebuild:compatibilitymkdirp buildprei18n-sync:testcd packages/i18n-sync && npm installprerjp:testcd packages/realistic-job-preview && npm installpretestnpm run lintpretraitify:testnpm run traitify:lintrjp:devcd packages/realistic-job-preview && npm run dev --rjp:testcd packages/realistic-job-preview && npm run test --testnpm-run-all *:testtraitify:linteslint {src,test}traitify:testjest --config test/jest.config.js --coveragetraitify:test:watchjest --config test/jest.config.js --watch
Dependencies9
@fortawesome/fontawesome-svg-core^6.5.2@fortawesome/free-solid-svg-icons^6.5.2bowser^2.13.1color^4.2.3core-js^3.37.1markdown-to-jsx^7.4.7prop-types^15.8.1recoil^0.7.7regenerator-runtime^0.14.1