gitsafehub
github.com/timqian/blockchain-playground ↗

timqian/blockchain-playground

scanned 2026-08-05 · git d59d489
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secretsVulnerable dependencies16Known OSS vulnerabilities15Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivy 16 found · 2 serious

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

  • Serious CVE-2023-46233 crypto-js: PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard
    package-lock.json
    A package you depend on has a known security hole (CVE-2023-46233). Fix: Update that package to its patched version.
  • Serious CVE-2025-9288 sha.js: Missing type checks leading to hash rewind and passing on crafted data
    package-lock.json
    A package you depend on has a known security hole (CVE-2025-9288). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-45590 body-parser: Denial of Service Vulnerability in body-parser
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-45590). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-29041 express: cause malformed URLs to be evaluated
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-29041). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-45296 path-to-regexp: Backtracking regular expressions cause ReDoS
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-45296). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-52798 path-to-regexp: path-to-regexp Unpatched `path-to-regexp` ReDoS in 0.1.x
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-52798). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-4867 path-to-regexp: path-to-regexp: Denial of Service via catastrophic backtracking from malformed URL parameters
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-4867). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-24999 express: "qs" prototype poisoning causes the hang of the node process
    package-lock.json
    A package you depend on has a known security hole (CVE-2022-24999). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-15284 qs: qs: Denial of Service via improper input validation in array parsing
    package-lock.json
    A package you depend on has a known security hole (CVE-2025-15284). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-37890 nodejs-ws: denial of service when handling a request with many HTTP headers
    package-lock.json
    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
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-48779). Fix: Update that package to its patched version.
  • Minor CVE-2026-12590 body-parser: body-parser: Denial of Service via invalid limit option
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-12590). Fix: Update that package to its patched version.
  • Minor CVE-2024-47764 cookie: cookie accepts cookie name, path, and domain with out of bounds characters
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-47764). Fix: Update that package to its patched version.
  • Minor CVE-2024-43796 express: Improper Input Handling in Express Redirects
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-43796). Fix: Update that package to its patched version.
  • Minor CVE-2024-43799 send: Code Execution Vulnerability in Send Library
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-43799). Fix: Update that package to its patched version.
  • Minor CVE-2024-43800 serve-static: Improper Sanitization in serve-static
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-43800). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 15 found · 2 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-xwcq-pm8m-c4vf crypto-js PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2023-46233). Fix: Update that package to its patched version.
  • Serious GHSA-95m3-7q98-8xr5 sha.js is missing type checks leading to hash rewind and passing on crafted data
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2025-9288). Fix: Update that package to its patched version.
  • Worth fixing GHSA-qwcr-r2fm-qrc7 body-parser vulnerable to denial of service when url encoding is enabled
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-45590). Fix: Update that package to its patched version.
  • Worth fixing GHSA-qw6h-vgh9-j6wx express vulnerable to XSS via response.redirect()
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-43796). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rv95-896h-c2vc Express.js Open Redirect in malformed URLs
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-29041). Fix: Update that package to its patched version.
  • Worth fixing GHSA-37ch-88jc-xwx2 path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-45296). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rhx6-c78j-4q9w path-to-regexp contains a ReDoS
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-52798). Fix: Update that package to its patched version.
  • Worth fixing GHSA-6rw7-vpxm-498p qs's arrayLimit bypass in its bracket notation allows DoS via memory exhaustion
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2025-15284). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hrpp-h998-j3pp qs vulnerable to Prototype Pollution
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2022-24999). Fix: Update that package to its patched version.
  • Worth fixing GHSA-m6fv-jmcg-4jfg send vulnerable to template injection that can lead to XSS
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-43799). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cm22-4g7w-348p serve-static vulnerable to template injection that can lead to XSS
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-43800). Fix: Update that package to its patched version.
  • Worth fixing GHSA-3h5v-q93c-6h6q ws affected by a DoS when handling a request with many HTTP headers
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-37890). 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-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2026-48779). Fix: Update that package to its patched version.
  • Minor GHSA-v422-hmwv-36x6 body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2026-12590). Fix: Update that package to its patched version.
  • Minor GHSA-pxg6-pf52-xh8x cookie accepts cookie name, path, and domain with out of bounds characters
    /workdirs/scan-103695cf-b916-4d4e-bb2b-af56ace0d0cb/package-lock.json
    A package you depend on has a known security hole (CVE-2024-47764). 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 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.