PkgRadar

Package evidence

@async/[email protected]

Suspicious Publish Context: {"package_age_days":0,"publisher":"patrickjs","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"async"},"version_anomaly":false,"new_account":false}

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
5
First published
Jun 2026
Publisher
patrickjs

Recommended action

Review before promoting

Mixed 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":["@async/[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":["@async/[email protected]"],"fail_on":"review"}'
Publisherpatrickjs
Artifact bytes52,522
Previous version0.0.5
Published2026-06-14T17:33:39.262Z
SHA-25632a07736b8699c538fde3e733ebb622a120611a8d47896397fdc802bcfb8414e

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":0,"publisher":"patrickjs","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"async"},"version_anomaly":false,"new_account":false}

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
10Score
0.0.6Version
Status history (1 event)
  1. newavailable · risk review · score 10 · status changed

Evidence

Static findings

1 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":0,"publisher":"patrickjs","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"async"},"version_anomaly":false,"new_account":false}10

Manifest

Package metadata

Scripts40
  • consolenode src/cli.js console
  • pipeline:api:checkasync-pipeline run-task api.check
  • pipeline:api:surfaceasync-pipeline run-task api.surface
  • pipeline:github:checkasync-pipeline github check
  • pipeline:github:generateasync-pipeline github generate
  • pipeline:pack:checkasync-pipeline run-task pack.check
  • pipeline:pagesasync-pipeline run pages
  • pipeline:previewasync-pipeline run preview
  • pipeline:publishasync-pipeline run publish
  • pipeline:publish:github:mainasync-pipeline publish github main --package .
  • pipeline:publish:github:prasync-pipeline publish github pr --package .
  • pipeline:publish:github:releaseasync-pipeline publish github release --package .
  • pipeline:publish:npmasync-pipeline publish npm --package .
  • pipeline:release-doctorasync-pipeline run release-doctor
  • pipeline:release:doctorasync-pipeline release doctor --package .
  • pipeline:release:ensureasync-pipeline release ensure --package .
  • pipeline:skills:checkasync-pipeline run-task skills.check
  • pipeline:snapshotasync-pipeline run snapshot
  • pipeline:sync:checkasync-pipeline sync check
  • pipeline:sync:generateasync-pipeline sync generate
  • pipeline:task:api.checkasync-pipeline run-task api.check
  • pipeline:task:api.surfaceasync-pipeline run-task api.surface
  • pipeline:task:buildasync-pipeline run-task build
  • pipeline:task:claimsasync-pipeline run-task claims
  • pipeline:task:claims.reportasync-pipeline run-task claims.report
  • pipeline:task:docs.siteasync-pipeline run-task docs.site
  • pipeline:task:github.checkasync-pipeline run-task github.check
  • pipeline:task:pack.checkasync-pipeline run-task pack.check
  • pipeline:task:publish.previewasync-pipeline run-task publish.preview
  • pipeline:task:publish.snapshotasync-pipeline run-task publish.snapshot
  • …and 10 more.