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.
- Versions published
- 2
- First published
- Jun 2026
- Publisher
- lfdt-npm
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":["@hyperledger-cacti/[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":["@hyperledger-cacti/[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
Scripts5
watchnpm-watchwebpacknpm-run-all webpack:devwebpack:devnpm-run-all webpack:dev:node webpack:dev:webwebpack:dev:nodewebpack --env=dev --target=node --config ../../webpack.config.jswebpack:dev:webwebpack --env=dev --target=web --config ../../webpack.config.js
Dependencies7
@hyperledger-cacti/cactus-common3.0.0-alpha.5@hyperledger-cacti/cactus-test-tooling3.0.0-alpha.5dockerode3.3.0internal-ip6.2.0run-time-error-cjs1.4.0web34.0.3web3-eth-accounts4.0.3