PkgRadar

Package evidence

@types/[email protected]

no findings

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
Sep 2024
Publisher
types

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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":["@types/[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":["@types/[email protected]"],"fail_on":"review"}'
Publishertypes
Artifact bytes3,118
Previous versionnone
Published2024-09-11T09:36:55.301Z
SHA-256a5aca0fbc109354dc6eee0c5196231e5a362312a3c0b742101096c5ad386b1ce

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

low
Last checked
lowRisk
0Score
1.6.0Version
Status history (2 events)
  1. available → available · risk low · score 0 · status available -> available, risk high -> low, score 35 -> 0
  2. new → available · risk high · score 35 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Dependencies2
  • puppeteer*
  • sharp*