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
8,131Niche · −30% score
Versions published
77
First published
Jun 2026
Publisher
agentic-in

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"}'
Publisheragentic-in
Artifact bytes696,499
Previous version0.14.4-dev.103.f2d2366
Published2026-06-12T10:19:56.422Z
SHA-256a57e56ca924f962228225c9f022b93233445fd37b1fdf4cffb5fe11876e1b5d7

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.14.4-dev.104.3e2b513Version
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

Scripts22
  • buildtsc -p tsconfig.json
  • checktsc --noEmit -p tsconfig.json
  • experiment:long-horizonnpm run build && node scripts/long-horizon-value.mjs
  • prepacknpm run build
  • site:buildnpm --prefix website run build
  • site:servenpm --prefix website run serve
  • site:startnpm --prefix website run start
  • testnpm run build && node --test dist/test/*.test.js
  • validate:allnpm run build && for milestone in T0 T1 T2 T3 T4 T5 T6 T7 T8 T9 T10; do node dist/src/validation/milestone.js $milestone || exit 1; done
  • validate:omni-e2e-runtimenpm run build && node dist/src/validation/omni-e2e-runtime.js
  • validate:omni-realnpm run build && node dist/src/validation/omni-real-smoke.js
  • validate:t0npm run build && node dist/src/validation/milestone.js T0
  • validate:t1npm run build && node dist/src/validation/milestone.js T1
  • validate:t10npm run build && node dist/src/validation/milestone.js T10
  • validate:t2npm run build && node dist/src/validation/milestone.js T2
  • validate:t3npm run build && node dist/src/validation/milestone.js T3
  • validate:t4npm run build && node dist/src/validation/milestone.js T4
  • validate:t5npm run build && node dist/src/validation/milestone.js T5
  • validate:t6npm run build && node dist/src/validation/milestone.js T6
  • validate:t7npm run build && node dist/src/validation/milestone.js T7
  • validate:t8npm run build && node dist/src/validation/milestone.js T8
  • validate:t9npm run build && node dist/src/validation/milestone.js T9
Dependencies4
  • @colbymchenry/codegraph0.9.9
  • commander^14.0.2
  • typescript^5.9.3
  • yaml^2.8.1