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
6
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.

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":["@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 bytes55,048
Previous version0.3.0
Published2026-06-17T10:14:21.487Z
SHA-256dc85156df2fcd9c3ad2e3c1dc3b39a1a361cb07ea1b953681d0c331e8b52eb85

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.4.0Version
Status history (1 event)
  1. new → available · 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

Scripts21
  • async-pipelineasync-pipeline
  • bundlenode scripts/build-framework-bundle.js
  • bundle:checknode scripts/build-framework-bundle.js --check
  • docs:buildnode scripts/build-pages.js
  • examplesnode --test tests/examples.test.js
  • examples:checknode --test tests/examples.test.js
  • pack:checkpnpm run bundle:check && npm pack --dry-run --ignore-scripts
  • pipeline:github:checkasync-pipeline github check
  • pipeline:github:generateasync-pipeline github generate
  • pipeline:pagesasync-pipeline run pages
  • pipeline:publishasync-pipeline run publish
  • 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:sync:checkasync-pipeline sync check
  • pipeline:sync:generateasync-pipeline sync generate
  • pipeline:task:docs.siteasync-pipeline run-task docs.site
  • pipeline:verifyasync-pipeline run verify
  • release:checkpnpm run pipeline:verify -- --force && pnpm run pipeline:pages -- --force && pnpm run pipeline:sync:check && pnpm run pipeline:github:check
  • testnode --test tests/*.test.js