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
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

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"}'
Publisherbeingmartinbmc
Artifact bytes355,669
Previous version5.0.2
Published2026-05-15T04:39:36.681Z
SHA-2561b9ea1bfe46d6717172436ce084e3d4297f594f15e086072d53ca8bb224dc0f5

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
5.0.3Version
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
  • audit:prodnpm audit --omit=dev --audit-level=moderate
  • buildnpm run build:backend && npm run build:frontend && npm run copy-frontend
  • build:backendtsc -p tsconfig.json
  • build:frontendnpm run --prefix frontend -s build -- --configuration production
  • build:productionNODE_ENV=production npm run build
  • cleanrm -rf dist build coverage frontend/dist frontend/.angular
  • copy-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.ts
  • dev:frontendnpm run --prefix frontend start -- --port 4200 --proxy-config proxy.conf.json
  • formatprettier --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" --fix
  • preparehusky
  • prepublishOnlynpm run clean && npm run lint && npm run typecheck && npm test -- --ci && npm run audit:prod && npm run build
  • startnode dist/backend/server.js
  • start:productionNODE_ENV=production node dist/backend/server.js
  • testjest
  • test:coveragejest --coverage
  • test:watchjest --watch
  • typechecktsc -p tsconfig.json --noEmit
Dependencies8
  • chalk^4.1.2
  • commander^12.1.0
  • compression^1.7.4
  • cors^2.8.5
  • express^4.21.0
  • express-rate-limit^7.4.0
  • helmet^8.0.0
  • open^8.4.2
Optional dependencies1
  • better-sqlite3^12.9.0