Package evidence

@signalapp/[email protected]

Install-time lifecycle script: install="echo Use \\`npm run build\\` to build the native library if needed"

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: 24,061Mainstream · −50% score
Versions published: 192Mature · −50% score
First published: Mar 2022
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.

Inspect tarball Add to CI gate

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":["@signalapp/[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":["@signalapp/[email protected]"],"fail_on":"review"}'

PublisherGitHub Actions

Artifact bytes138,616,406

Previous version0.96.0

Published2026-06-15T16:53:18.088Z

SHA-256

Why flagged

What the scanner saw

Install-time lifecycle script: install="echo Use \\`npm run build\\` to build the native library if needed"

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

Availability ledger

available

review

8h agoLast checked

reviewRisk

1Score

0.96.1Version

Status history (2 events)

scan_error → available8h ago · risk review · score 1 · status scan_error -> available, risk none -> review, score none -> 1
new → scan_error8h ago · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@signalapp/libsignal-client/-/libsignal-client-0.96.1.tgz)

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)

Severity	Kind	Path	Detail	Points
low	Install-time lifecycle script	package.json	install="echo Use \\`npm run build\\` to build the native library if needed"	5
low	Oversized Unscanned	manifest	tarball exceeds the 50MB fetch cap; scanned registry metadata (install scripts + dependencies) only	0

Manifest

Package metadata

Scripts11

buildpython3 build_node_bridge.py
build-with-debug-level-logspython3 build_node_bridge.py --debug-level-logs
cleanrimraf dist build prebuilds
formatp() { prettier ${@:- --write} '**/*.{css,js,json,md,scss,ts,tsx}'; }; p
format-checkp() { prettier ${@:- --check} '**/*.{css,js,json,md,scss,ts,tsx}'; }; p
format-stdinprettier
installecho Use \`npm run build\` to build the native library if needed
linteslint .
prepackcp ../acknowledgments/acknowledgments-desktop.md dist/acknowledgments.md
testmocha --recursive dist/test --require source-map-support/register
tsctsc -b

Dependencies2

node-gyp-build^4.8.0
type-fest^4.26.0