gitsafehub
github.com/chopmob-cloud/algovoi-rfc9421-verifier ↗

chopmob-cloud/algovoi-rfc9421-verifier

scanned 2026-08-11 · git ed09be7
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 secrets1Vulnerable dependencies✓Known OSS vulnerabilities12Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ 1 found

API keys, passwords or tokens committed into the repo.

  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    python/tests/test_verifier.py:222
    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ⓘ none found ✓

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

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 12 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-5xrq-8626-4rwp When Vitest UI server is listening, arbitrary file can be read and executed
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-47429). Fix: Update that package to its patched version.
  • Worth fixing GHSA-3jxr-9vmj-r5cp brace-expansion: DoS via exponential-time expansion of consecutive non-expanding {} groups
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-13149). Fix: Update that package to its patched version.
  • Worth fixing GHSA-mh99-v99m-4gvg brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-14257). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rgw5-rvv9-x895 brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-69152). Fix: Update that package to its patched version.
  • Worth fixing GHSA-67mh-4wv8-2f99 esbuild enables any website to send any requests to the development server and read the response
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-28wg-ghj8-5hjv nanoid: non-secure generators can loop indefinitely with negative size
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-67214). Fix: Update that package to its patched version.
  • Worth fixing GHSA-2v37-7h3g-55p8 nanoid: custom generators can loop indefinitely when size is zero
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-67213). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fxqj-rqcc-2cmp PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-69153). Fix: Update that package to its patched version.
  • Worth fixing GHSA-r28c-9q8g-f849 PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-4w7w-66w2-5vf9 Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-39365). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fx2h-pf6j-xcff vite: `server.fs.deny` bypass on Windows alternate paths
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-53571). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v6wh-96g9-6wx3 launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows
    /workdirs/scan-914f4df2-62f2-4c1c-86da-4bd2587ed540/typescript/package-lock.json
    A package you depend on has a known security hole (CVE-2026-53632). 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.