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
- 3,302Niche · −30% score
- Versions published
- 819Mature · −50% score
- First published
- Sep 2024
- 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
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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
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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts9
buildts-builder build --target node --build-config ./build.node.config.jscheckts-builder check --target nodedo-packrm -f *.tgz && pnpm pack && mv *.tgz package.tgzfmtts-builder formatformatter:checkts-builder formatter --checklinter:checkts-builder linter --checktestvitest run --coveragetypes:checkts-builder type-check --target nodewatchts-builder build --target node --build-config ./build.node.config.js --watch
Dependencies30
@milaboratories/computable2.9.5@milaboratories/helpers1.14.2@milaboratories/pf-driver1.7.4@milaboratories/pf-spec-driver1.4.6@milaboratories/pframes-rs-node1.1.42@milaboratories/pframes-rs-wasm1.1.42@milaboratories/pl-client3.11.3@milaboratories/pl-deployments3.0.6@milaboratories/pl-drivers1.15.5@milaboratories/pl-errors1.4.21@milaboratories/pl-http1.2.4@milaboratories/pl-model-backend1.4.6@milaboratories/pl-model-common1.46.0@milaboratories/pl-model-middle-layer1.30.0@milaboratories/pl-tree1.12.11@milaboratories/resolve-helper1.1.3@milaboratories/ts-helpers1.8.3@platforma-sdk/block-tools2.10.9@platforma-sdk/model1.78.9@platforma-sdk/workflow-tengo6.3.2canonicalize~2.1.0denque^2.1.0es-toolkit^1.39.10lru-cache^11.2.2quickjs-emscripten0.31.0semver^7.7.2undici~7.16.0utility-types^3.11.0yaml^2.8.0zod~3.25.76