PkgRadar

Package evidence

@synapseia-network/[email protected]

Install-time lifecycle script: postinstall="patch-package"

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
134
First published
May 2026
Publisher
GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: 70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Review before promoting

Mixed 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":["@synapseia-network/[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":["@synapseia-network/[email protected]"],"fail_on":"review"}'
Artifact bytes2,811,839
Previous version0.9.12
Published2026-06-08T19:20:42.635Z
SHA-2560eaee3324305f3e97f3dd471508e3a0b5b6a1074df7848e56b89ccfd2dc389ab

Why flagged

What the scanner saw

Install-time lifecycle script: postinstall="patch-package"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
1Score
0.9.13Version
Status history (1 event)
  1. newavailable · risk review · score 1 · status changed

Evidence

Static findings

2 static · 0 from release diff · showing high-signal first.

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowInstall-time lifecycle scriptpackage.jsonpostinstall="patch-package"5
lowLarge Javascript Payloadpackage/dist/index.js14986754 bytes0

Manifest

Package metadata

Scripts9
  • buildtsup
  • devtsup index.ts --watch --onSuccess "node dist/bootstrap.js --help"
  • linteslint src
  • postinstallpatch-package
  • preparenpm run build
  • startnode dist/bootstrap.js
  • testjest
  • test:diloco-compatPY=$([ -x /opt/training-venv/bin/python ] && echo /opt/training-venv/bin/python || command -v python3); echo "[diloco-compat] python=$PY"; "$PY" -c 'import torch;print("[diloco-compat] torch=="+torch.__version__)'; echo '[diloco-compat] AUTHORITATIVE pre-release run MUST use the pinned torch==2.5.1 venv (/opt/training-venv); other torch versions are smoke-only'; "$PY" scripts/diloco_compat_smoke.py && "$PY" -m pytest scripts/__tests__/diloco_aggregate_executor_test.py -q
  • test:mutationNODE_OPTIONS=--experimental-vm-modules stryker run
Dependencies41
  • @inquirer/prompts8.4.3
  • @langchain/core1.1.47
  • @langchain/langgraph1.3.2
  • @langfuse/langchain5.3.0
  • @langfuse/otel5.3.0
  • @langfuse/tracing5.3.0
  • @libp2p/bootstrap12.0.22
  • @libp2p/crypto5.1.18
  • @libp2p/gossipsub15.0.23
  • @libp2p/identify4.1.6
  • @libp2p/kad-dht16.2.7
  • @libp2p/noise1.0.1
  • @libp2p/ping3.1.5
  • @libp2p/tcp11.0.20
  • @libp2p/utils7.1.0
  • @libp2p/yamux8.0.1
  • @multiformats/multiaddr13.0.3
  • @nestjs/axios4.0.1
  • @nestjs/common11.1.23
  • @nestjs/config4.0.4
  • @nestjs/core11.1.23
  • @noble/ed255193.1.0
  • @noble/hashes2.2.0
  • @opentelemetry/sdk-node0.215.0
  • @solana/spl-token0.4.14
  • @solana/web3.js1.98.4
  • @types/bip393.0.4
  • axios1.16.1
  • bip393.1.0
  • bs586.0.0
  • …and 11 more.