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
- 82
- 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
Scripts6
buildyarn run tscdevnodemon out/server.jsstartnode out/server.jstestnyc mocha -r ts-node/register --exclude 'test/data/**/*.js' --recursive -t 10000tsctscwatchtsc --watch
Dependencies9
@fidm/x5091.2.1@grpc/grpc-js1.13.3@hyperledger-cacti/cacti-weaver-protos-js3.0.0-alpha.5@hyperledger-cacti/cacti-weaver-sdk-fabric3.0.0-alpha.5dotenv8.6.0fabric-ca-client2.2.20fabric-common2.2.20fabric-network2.2.20uuid10.0.0