gitsafehub
github.com/consensys-archive/uws-js-unofficial ↗

consensys-archive/uws-js-unofficial

scanned 2026-08-14 · git 96ab8d7
3 of 6 checks flagged a security issue
🔴 Needs attention
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets3Vulnerable dependencies3Known OSS vulnerabilities3Risky code patterns✓Malicious dependencies—Project health—

Security checks

Leaked secrets — Gitleaksⓘ 3 found · 3 serious

API keys, passwords or tokens committed into the repo.

  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    misc/key.pem:1
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    misc/key.pem:1
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    misc/key.pem:1
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 3 found

Packages you depend on that have known security holes (CVEs).

  • Worth fixing CVE-2024-37890 nodejs-ws: denial of service when handling a request with many HTTP headers
    yarn.lock
    A package you depend on has a known security hole (CVE-2024-37890). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-48779 ws: ws: Denial of Service via memory exhaustion from small WebSocket fragments
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-48779). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-45736 ws: ws: Uninitialized memory disclosure via `websocket.close()` with `TypedArray`
    yarn.lock
    A package you depend on has a known security hole (CVE-2026-45736). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 3 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-3h5v-q93c-6h6q ws affected by a DoS when handling a request with many HTTP headers
    /workdirs/scan-c1ec8a50-d9b2-46d3-865f-ca2ae7dbff9a/yarn.lock
    A package you depend on has a known security hole (CVE-2024-37890). Fix: Update that package to its patched version.
  • Worth fixing GHSA-58qx-3vcg-4xpx ws: Uninitialized memory disclosure
    /workdirs/scan-c1ec8a50-d9b2-46d3-865f-ca2ae7dbff9a/yarn.lock
    A package you depend on has a known security hole (CVE-2026-45736). Fix: Update that package to its patched version.
  • Worth fixing GHSA-96hv-2xvq-fx4p ws: Memory exhaustion DoS from tiny fragments and data chunks
    /workdirs/scan-c1ec8a50-d9b2-46d3-865f-ca2ae7dbff9a/yarn.lock
    A package you depend on has a known security hole (CVE-2026-48779). Fix: Update that package to its patched version.

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ timed out

Packages that look intentionally malicious: typosquats, sneaky install scripts.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Guarddog v2.10.0 · Apache-2.0

error: npm:timeout

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ didn’t run

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.