Package evidence
@milaboratories/[email protected]
Install-time lifecycle script: install="node-pre-gyp install --update-binary --fallback-to-build=false || node -p \"process.exit(+!(require('./package.json').version === '0.0.0'))\""
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,502Niche · −30% score
- Versions published
- 130Mature · −50% score
- First published
- Jan 2025
- Publisher
- mike-ainsel
Effective trust discount applied: −50% (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":["@milaboratories/[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":["@milaboratories/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Install-time lifecycle script: install="node-pre-gyp install --update-binary --fallback-to-build=false || node -p \"process.exit(+!(require('./package.json').version === '0.0.0'))\""
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 2 · 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 | install="node-pre-gyp install --update-binary --fallback-to-build=false || node -p \"process.exit(+!(require('./package.json').version === '0.0.0'))\"" | 5 |
Manifest
Package metadata
Scripts22
buildpnpm run build:rust && pnpm run build:tsbuild:rustshx mkdir -p dist/napi-v8 && cargo build -p pframes_rs_nodebuild:tsts-builder build --target node --build-config build.node.config.jsbump-versioncargo run -p pframes_rs_meta --bin npm_version -r --lockedcheckpnpm run check:tscheck:tsts-builder linter --check --target node && ts-builder formatter --checkci-buildpnpm run build:rust -r --locked && pnpm run build:tsci-testpnpm run ci-test:ts && pnpm run ci-test:rustci-test:rustpnpm run test:nextest -r --locked && pnpm run test:rustdoc -r --lockedci-test:tsts-builder type-check --target node --project tsconfig.check.json && pnpm exec vitest run --coveragefixpnpm run fix:tsfix:tsts-builder formatinstallnode-pre-gyp install --update-binary --fallback-to-build=false || node -p "process.exit(+!(require('./package.json').version === '0.0.0'))"packpnpm exec node-pre-gyp package && pnpm exec node-pre-gyp reveal staged_tarball --silentpostbuild:tspnpm exec rimraf package.tgz && pnpm pack --out package.tgzpreci-testpnpm run ci-buildpretestpnpm run buildtestpnpm run test:ts && pnpm run test:rusttest:nextestcargo nextest run --no-tests passtest:rustpnpm run test:nextest && pnpm run test:rustdoctest:rustdoccargo doc --no-deps --document-private-itemstest:tspnpm run ci-test:ts
Dependencies5
@mapbox/node-pre-gyp2.0.3@milaboratories/helpers1.14.2@milaboratories/pframes-rs-serv1.1.46@milaboratories/pl-model-common1.46.1ulid3.0.2