PkgRadar

Package evidence

[email protected]

Credential file access: matched ".npmrc"

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
8,826Niche · −30% score
Versions published
102
First published
Jun 2026
Publisher
elya_livshitz

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

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":["[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"}'
Publisherelya_livshitz
Artifact bytes861,888
Previous version0.94.36
Published2026-06-16T10:16:38.420Z
SHA-256d95090ddf935c2de540813327e65c4910871b54f88fd17597164238e7b879cb7

Why flagged

What the scanner saw

Credential file access: matched ".npmrc"

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

Availability ledger

available

review
Last checked
reviewRisk
7Score
0.94.37Version
Status history (2 events)
  1. scan_error → available · risk review · score 7 · status scan_error -> available, risk none -> review, score none -> 7
  2. new → scan_error · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/agent.libx.js/-/agent.libx.js-0.94.37.tgz)

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/cli.jsmatched ".npmrc"5
lowCredential file accesspackage/dist/index.jsmatched ".npmrc"5

Manifest

Package metadata

Scripts9
  • buildtsup
  • clibun cli/cli.ts
  • prepublishOnlybun run build
  • qa:ttybun test tests/cli-tty.test.ts
  • testtimeout -k 10 600 bun test
  • test:redteambun test tests/jail.test.ts tests/symlink.test.ts tests/sandbox.test.ts
  • test:uicd web && bun run test:ui
  • test:watchbun test --watch
  • typechecktsc -p tsconfig.typecheck.json
Dependencies4
  • @bod.ee/db^2.14.3
  • @livx.cc/wcli^2.2.5
  • ai.libx.js^0.17.4
  • libx.js^6.3.0