Package evidence
@agentrix/[email protected]
Install-time lifecycle script: postinstall="node scripts/ensure-better-sqlite3.cjs"
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
- 1,346Niche · −30% score
- Versions published
- 62
- First published
- Feb 2026
- Publisher
- xmz.ai
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 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":["@agentrix/[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":["@agentrix/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Install-time lifecycle script: postinstall="node scripts/ensure-better-sqlite3.cjs"
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 3 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Install-time lifecycle script | package.json | postinstall="node scripts/ensure-better-sqlite3.cjs" | 5 |
Manifest
Package metadata
Scripts12
buildshx rm -rf dist && tsc --noEmit --skipLibCheck 2>&1 | (grep -v 'node_modules/effect' | grep -v 'Symbol.dispose' || true) && pkgroll && shx mkdir -p dist/sandbox && shx cp src/sandbox/node-proxy-boot.cjs dist/sandbox/ && shx mkdir -p dist/migrations && shx cp src/worker/history/migrations/*.sql dist/migrations/ && node scripts/minify-dist.mjsdevyarn build && tsx --env-file .env.dev src/index.tslinteslint 'src/**/*.{js,ts}' --fixlocalyarn build && tsx --env-file .env.local src/index.tspostinstallnode scripts/ensure-better-sqlite3.cjsprepublishOnlyyarn build && yarn testprodnode --env-file=.env ./bin/agentrix.mjsprod-localyarn build && tsx --env ./bin/agentrix.mjsreleaserelease-ittestyarn build && tsx --env-file .env.integration-test node_modules/.bin/vitest runtypechecktsc --noEmit --skipLibCheck 2>&1 | (grep -v 'node_modules/effect' | grep -v 'Symbol.dispose' || true)why do we need to build before running tests / dev?We need the binary to be built so we run daemon commands which directly run the binary
Dependencies47
@agentrix/shared^2.38.0@anthropic-ai/claude-agent-sdk^0.2.133@anthropic-ai/sdk0.71.2@larksuiteoapi/node-sdk^1.63.1@modelcontextprotocol/sdk^1.15.1@openai/codex-sdk^0.133.0@stablelib/base64^2.0.1@stablelib/hex^2.0.1@types/better-sqlite3^7.6.13@types/cross-spawn^6.0.6@types/http-proxy^1.17.16@types/ps-list^6.2.1@types/qrcode-terminal^0.12.2@types/react^19.1.9@types/tmp^0.2.6@types/yargs^17.0.33@xmz-ai/sandbox-runtime^0.2.5axios1.13.2better-sqlite3^12.6.2chalk^5.4.1croner^9.0.0cross-spawn^7.0.6expo-server-sdk^3.15.0fastify^5.5.0fastify-type-provider-zod^6.1.0http-proxy^1.18.1http-proxy-middleware^3.0.5ink^6.1.0ink-box^2.0.0ink-select-input^6.0.0- …and 17 more.
Optional dependencies1
node-datachannel0.9.1