gitsafehub
github.com/paritytech/parity-bridges-common ↗

paritytech/parity-bridges-common

scanned 2026-08-15 · git 0e34aac
1 of 6 checks flagged a security issue
🟡 Worth a look
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets—Vulnerable dependencies17Known OSS vulnerabilities✓Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ timed out

API keys, passwords or tokens committed into the repo.

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

via Gitleaks v8.21.2 · MIT

error: timeout after 120s

Vulnerable dependencies — Trivyⓘ 17 found

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

  • Worth fixing GHSA-q2qq-hmj6-3wpp hickory-proto vulnerable to CPU exhaustion during message encoding due to O(n²) name compression
    Cargo.lock
    A package you depend on has a known security hole (GHSA-q2qq-hmj6-3wpp). Fix: Update that package to its patched version.
  • Worth fixing GHSA-q2qq-hmj6-3wpp hickory-proto vulnerable to CPU exhaustion during message encoding due to O(n²) name compression
    Cargo.lock
    A package you depend on has a known security hole (GHSA-q2qq-hmj6-3wpp). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-4432 ring: Some AES functions may panic when overflow checking is enabled in ring
    Cargo.lock
    A package you depend on has a known security hole (CVE-2025-4432). Fix: Update that package to its patched version.
  • Worth fixing GHSA-82j2-j2ch-gfr8 rustls-webpki: Denial of service via panic on malformed CRL BIT STRING
    Cargo.lock
    A package you depend on has a known security hole (GHSA-82j2-j2ch-gfr8). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-32314 Yamux is a stream multiplexer over reliable, ordered connections such ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2026-32314). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-12224 idna: idna accepts Punycode labels that do not produce any non-ASCII when decoded
    tools/runtime-codegen/Cargo.lock
    A package you depend on has a known security hole (CVE-2024-12224). Fix: Update that package to its patched version.
  • Worth fixing GHSA-qg5g-gv98-5ffh rustls network-reachable panic in `Acceptor::accept`
    tools/runtime-codegen/Cargo.lock
    A package you depend on has a known security hole (GHSA-qg5g-gv98-5ffh). Fix: Update that package to its patched version.
  • Worth fixing GHSA-82j2-j2ch-gfr8 rustls-webpki: Denial of service via panic on malformed CRL BIT STRING
    tools/runtime-codegen/Cargo.lock
    A package you depend on has a known security hole (GHSA-82j2-j2ch-gfr8). Fix: Update that package to its patched version.
  • Worth fixing GHSA-pwjx-qhcg-rvj4 webpki: CRLs not considered authoritative by Distribution Point due to faulty matching logic
    tools/runtime-codegen/Cargo.lock
    A package you depend on has a known security hole (GHSA-pwjx-qhcg-rvj4). Fix: Update that package to its patched version.
  • Minor GHSA-rhfx-m35p-ff5j `IterMut` violates Stacked Borrows by invalidating internal pointer
    Cargo.lock
    A package you depend on has a known security hole (GHSA-rhfx-m35p-ff5j). Fix: Update that package to its patched version.
  • Minor GHSA-cq8v-f236-94qc Rand is unsound with a custom logger using rand::rng()
    Cargo.lock
    A package you depend on has a known security hole (GHSA-cq8v-f236-94qc). Fix: Update that package to its patched version.
  • Minor GHSA-965h-392x-2mh5 webpki: Name constraints for URI names were incorrectly accepted
    Cargo.lock
    A package you depend on has a known security hole (GHSA-965h-392x-2mh5). Fix: Update that package to its patched version.
  • Minor GHSA-xgp8-3hg3-c2mh webpki: Name constraints were accepted for certificates asserting a wildcard name
    Cargo.lock
    A package you depend on has a known security hole (GHSA-xgp8-3hg3-c2mh). Fix: Update that package to its patched version.
  • Minor CVE-2025-58160 tracing-subscriber: Tracing log pollution
    Cargo.lock
    A package you depend on has a known security hole (CVE-2025-58160). Fix: Update that package to its patched version.
  • Minor GHSA-965h-392x-2mh5 webpki: Name constraints for URI names were incorrectly accepted
    tools/runtime-codegen/Cargo.lock
    A package you depend on has a known security hole (GHSA-965h-392x-2mh5). Fix: Update that package to its patched version.
  • Minor GHSA-xgp8-3hg3-c2mh webpki: Name constraints were accepted for certificates asserting a wildcard name
    tools/runtime-codegen/Cargo.lock
    A package you depend on has a known security hole (GHSA-xgp8-3hg3-c2mh). Fix: Update that package to its patched version.
  • Minor CVE-2025-58160 tracing-subscriber: Tracing log pollution
    tools/runtime-codegen/Cargo.lock
    A package you depend on has a known security hole (CVE-2025-58160). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ none found ✓

Your dependencies cross-checked against the OSV vulnerability database.

Nothing found by this check. ✓

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ⓘ none found ✓

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

Nothing found by this check. ✓

via Guarddog v2.10.0 · Apache-2.0

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.