Package evidence
@async/[email protected]
Suspicious Publish Context: {"package_age_days":0,"publisher":"patrickjs","burst_same_day":1,"burst_week":1,"lure":{"kind":"edit_distance","target":"json5"},"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
- 3
- First published
- Jun 2026
- Publisher
- patrickjs
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":["@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"}'Why flagged
What the scanner saw
Suspicious Publish Context: {"package_age_days":0,"publisher":"patrickjs","burst_same_day":1,"burst_week":1,"lure":{"kind":"edit_distance","target":"json5"},"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
Status history (1 event)
- new → available · risk review · score 10 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Suspicious Publish Context | manifest | {"package_age_days":0,"publisher":"patrickjs","burst_same_day":1,"burst_week":1,"lure":{"kind":"edit_distance","target":"json5"},"version_anomaly":false,"new_account":false} | 10 |
Manifest
Package metadata
Scripts32
api-surface:checkapi-contract check --manifest api-contract.json && api-contract ledger --manifest api-contract.json --check API_SURFACE.mdapi-surface:generateapi-contract ledger --manifest api-contract.json --out API_SURFACE.mdbench:stable-jsonpnpm run build && node ./scripts/bench-stable-json.jsbuildtsc -p tsconfig.jsonpack:checknpm --cache .async/npm-cache pack --dry-runpipeline:github:checkasync-pipeline github checkpipeline:github:generateasync-pipeline github generatepipeline:pagesasync-pipeline run pagespipeline:previewasync-pipeline run previewpipeline:publishasync-pipeline run publishpipeline:publish-githubasync-pipeline run publish-githubpipeline: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-doctorpipeline:release:doctorasync-pipeline release doctor --package .pipeline:release:ensureasync-pipeline release ensure --package .pipeline:snapshotasync-pipeline run snapshotpipeline:sync:checkasync-pipeline sync checkpipeline:sync:generateasync-pipeline sync generatepipeline:task:api-surfaceasync-pipeline run-task api-surfacepipeline:task:buildasync-pipeline run-task buildpipeline:task:docs.siteasync-pipeline run-task docs.sitepipeline:task:packasync-pipeline run-task packpipeline:task:testasync-pipeline run-task testpipeline:verifyasync-pipeline run verifyrelease:checkpnpm run vendor:json5:check && pnpm run build && pnpm run test && pnpm run api-surface:check && pnpm run pack:checktestpnpm run build && node --test tests/*.test.jstypechecktsc --noEmit -p tsconfig.json- …and 2 more.