PkgRadar

Package evidence

@anyq/[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
3
First published
Dec 2025
Publisher
sns45

Recommended action

Looks clean — keep monitoring

No 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":["@anyq/[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":["@anyq/[email protected]"],"fail_on":"review"}'
Publishersns45
Artifact bytes90,684
Previous versionnone
Published2025-12-17T17:02:49.143Z
SHA-256e615bb11ac3fe38360c7a84e1d8f78399c8cd105a95489bea054aff2aad59725

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
0.1.0Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts5
  • buildbun build ./src/index.ts --outdir ./dist --target bun && bun run build:types
  • build:typestsc --emitDeclarationOnly --outDir dist
  • cleanrm -rf dist
  • testbun test
  • typechecktsc --noEmit
Dependencies2
  • @anyq/coreworkspace:*
  • kafkajs^2.2.4