PkgRadar

Package evidence

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

Weekly downloads
5,142Niche · −30% score
Versions published
116
First published
May 2026
Publisher
jkait

Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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":["[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":["[email protected]"],"fail_on":"review"}'
Publisherjkait
Artifact bytes1,305,731
Previous version2.13.9
Published2026-06-14T04:22:17.856Z
SHA-256d0ac52d58cfd4b2e5b82585508258a38fb5683e298ab2318ff32b2a2783cd8b3

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
2.13.10Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts19
  • buildnode scripts/build.mjs
  • build:tsctsc --noCheck
  • checktsc --noEmit && pnpm test && pnpm run check:architecture-boundaries && pnpm run check:provider-core-boundary && pnpm run check:provider-core-release-sync && pnpm run check:pet-core-boundary && pnpm run check:workspace-hygiene && pnpm run check:package-artifact
  • check:architecture-boundariesnode scripts/check-architecture-boundaries.mjs
  • check:package-artifactnpm run build && node scripts/check-package-artifact.mjs
  • check:pet-core-boundarynode scripts/check-pet-core-boundary.mjs
  • check:provider-core-boundarynode scripts/check-provider-core-boundary.mjs
  • check:provider-core-release-syncnode scripts/check-provider-core-release-sync.mjs
  • check:workspace-hygienenode scripts/check-workspace-hygiene.mjs
  • check:workspace-hygiene:strictnode scripts/check-workspace-hygiene.mjs --strict
  • clean:workspace-hygienenode scripts/clean-workspace-hygiene.mjs
  • devtsx watch src/index.ts
  • lintoxlint .
  • redteam:community-desensitizationtsx src/runtime/community/community-desensitization-red-team-cli.ts
  • redteam:community-sandboxtsx src/skills/permissions/community-sandbox-red-team-cli.ts
  • releasenode scripts/release.mjs
  • startnode dist/cli.js
  • testvitest run
  • test:watchvitest
Dependencies11
  • @agentclientprotocol/sdk^0.25.0
  • @napi-rs/canvas0.1.100
  • @xiaozhiclaw/pet-core0.1.1
  • @xiaozhiclaw/provider-core^0.1.14
  • better-sqlite3^12.10.0
  • dotenv^17.3.1
  • ioredis^5.11.1
  • mcporter^0.12.0
  • nanoid^5.1.5
  • pino^9.6.0
  • pino-pretty^13.0.0