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
- 3
- First published
- Jun 2026
- Publisher
- milosaysyolo
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":["@orqenix/[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":["@orqenix/[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
Scripts4
buildtsc -p tsconfig.jsongate:G38Avitest run test/G38A-gate-wrapper.test.ts --reporter verbosegate:G38Bvitest run test/G38B-gate-wrapper.test.ts --reporter verbosetestvitest run --coverage
Dependencies15
@chainsafe/libp2p-noise^16.0.0@chainsafe/libp2p-yamux^7.0.0@libp2p/crypto^5.0.0@libp2p/interface^2.0.0@libp2p/memory^1.1.0@libp2p/peer-id^5.0.0@libp2p/tcp^10.0.0@libp2p/websockets^9.0.0@multiformats/multiaddr^12.3.0@orqenix/mesh-transport-core^0.6.0it-length-prefixed^9.1.0it-pipe^3.0.1libp2p^2.0.0msgpackr^1.11.0uint8arrays^5.1.0