Package evidence
[email protected]
Install-time lifecycle script: postinstall="node scripts/check-native.js"
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
- 63
- Versions published
- 23Established · −30% score
- First published
- Aug 2025
- Publisher
- beingmartinbmc
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
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
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":"high"}'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":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 5.1.0 vs 5.0.3: "node scripts/check-native.js"
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 high · score 45 · status changed
Evidence
Static findings
1 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 5.1.0 vs 5.0.3: "node scripts/check-native.js" | 40 |
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 5.1.0 vs 5.0.3: "node scripts/check-native.js" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="node scripts/check-native.js" | 5 |
Manifest
Package metadata
Scripts23
audit:prodnpm audit --omit=dev --audit-level=moderatebuildnpm run build:backend && npm run build:frontend && npm run copy-frontendbuild:backendtsc -p tsconfig.jsonbuild:frontendnpm run --prefix frontend -s build -- --configuration productionbuild:productionNODE_ENV=production npm run buildcleanrm -rf dist build coverage frontend/dist frontend/.angularcopy-frontendrm -rf build/frontend && mkdir -p build/frontend && cp -r frontend/dist/frontend/browser/* build/frontend/devconcurrently -n backend,frontend -c blue,magenta "npm:dev:backend" "npm:dev:frontend"dev:backendts-node-dev --respawn --transpile-only src/backend/dev-server.tsdev:frontendnpm run --prefix frontend start -- --port 4200 --proxy-config proxy.conf.jsonformatprettier --write "src/**/*.{ts,js}" "frontend/src/**/*.{ts,html,css}"format:checkprettier --check "src/**/*.{ts,js}" "frontend/src/**/*.{ts,html,css}"linteslint "src/**/*.ts"lint:fixeslint "src/**/*.ts" --fixpostinstallnode scripts/check-native.jspreparehuskyprepublishOnlynpm run clean && npm run lint && npm run typecheck && npm test -- --ci && npm run audit:prod && npm run buildstartnode dist/backend/server.jsstart:productionNODE_ENV=production node dist/backend/server.jstestjesttest:coveragejest --coveragetest:watchjest --watchtypechecktsc -p tsconfig.json --noEmit
Dependencies8
chalk^4.1.2commander^12.1.0compression^1.7.4cors^2.8.5express^4.21.0express-rate-limit^7.4.0helmet^8.0.0open^8.4.2
Optional dependencies1
better-sqlite3^12.9.0