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
- 6
- First published
- Apr 2020
- Publisher
- fauxsoup
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":["@amdglobal/[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":["@amdglobal/[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
Scripts7
buildwebpack -p --progressdevwebpack -d --watchjestnode_modules/.bin/jest --env=jsdomlintnode_modules/.bin/eslint ./src/**/*.jsxstartnode ./scripts/start.jstag-and-publishnode ./scripts/publish.jstestnode_modules/.bin/jest --env=jsdom --watch
Dependencies8
comma-separated-values^3.6.4mammoth^1.4.11pdfjs-dist^2.3.200prop-types^15.5.10react-data-grid^5.0.5react-visibility-sensor^5.0.2three0.85.2xlsx^0.10.1