Package evidence
@redonvn/[email protected]
Install-time lifecycle script: postinstall="node scripts/postinstall.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
- 214
- Versions published
- 29
- First published
- May 2026
- Publisher
- haianh123bgln
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":["@redonvn/[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":["@redonvn/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Install-time lifecycle script: postinstall="node scripts/postinstall.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 5 · 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/postinstall.cjs" | 5 |
Manifest
Package metadata
Scripts21
buildtsc -p tsconfig.jsonbuild:devcross-env BUILD_ENV=dev npm run -s clean && cross-env BUILD_ENV=dev node scripts/write-build-info.cjs && tsc -p tsconfig.json && node scripts/copy-builtin-skills.cjs && npm run build:uibuild:prodcross-env BUILD_ENV=prod npm run -s clean && cross-env BUILD_ENV=prod node scripts/write-build-info.cjs && tsc -p tsconfig.json && node scripts/copy-builtin-skills.cjs && npm run build:uibuild:uicd ui && npm install && npm run buildbuild:watchtsc -p tsconfig.json --watchcleanrimraf distdevts-node --transpile-only src/cli/index.tsdev:logints-node --transpile-only src/cli/index.ts login --env devdev:servets-node --transpile-only src/cli/index.ts serve --port 8317dev:startts-node --transpile-only src/cli/index.ts startinstall:localnpm run build:dev && npm install -g . && node -e "const{cpSync,mkdirSync}=require('fs');mkdirSync(require('os').homedir()+'/.redai/ui',{recursive:true});cpSync('ui/dist',require('os').homedir()+'/.redai/ui/dist',{recursive:true,force:true});console.log('UI copied to ~/.redai/ui/dist')"postbuildnode scripts/copy-builtin-skills.cjspostinstallnode scripts/postinstall.cjsprebuildnode scripts/write-build-info.cjsprepublishOnlynode -e "if(!process.env.SKIP_PREPUBLISH_GUARD){console.error('\nUse `npm run publish:prod` or `npm run publish:dev` to ensure correct BUILD_ENV is baked.\nIf you really want to publish directly, set SKIP_PREPUBLISH_GUARD=1.\n');process.exit(1)}"prod:loginnode ./bin/redai.js login --env prodprod:servenode ./bin/redai.js serve --port 8317prod:startnode ./bin/redai.js startpublish:devnpm run build:dev && cross-env SKIP_PREPUBLISH_GUARD=1 npm publish --access public --tag devpublish:prodnpm run build:prod && cross-env SKIP_PREPUBLISH_GUARD=1 npm publish --access publicstartnode ./bin/redai.js
Dependencies12
@modelcontextprotocol/sdk^1.29.0@redonvn/cli-protocol^0.1.5@redonvn/redai-cli-sdk^0.1.7@vscode/ripgrep^1.15.9axios^1.7.7chalk^4.1.2fast-glob^3.3.2prompts^2.4.2socket.io-client^4.7.5undici^6.19.7ws^8.18.0zod^3.23.8
Optional dependencies2
@nut-tree-fork/nut-js^4.2.6screenshot-desktop^1.15.4