gitsafehub
github.com/jiegec/maze-routing ↗

jiegec/maze-routing

scanned 2026-08-12 · git caffb08
2 of 6 checks flagged a security issue
🟡 Worth a look
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets✓Vulnerable dependencies4Known OSS vulnerabilities4Risky code patterns✓Malicious dependencies✓Project 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ⓘ 4 found

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

  • Worth fixing CVE-2026-67213 nanoid: nanoid: Denial of Service via infinite loop in random ID generation
    visualizer/yarn.lock
    A package you depend on has a known security hole (CVE-2026-67213). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-67214 nanoid (Nano ID) before 5.1.16 contains an infinite loop in the custom ...
    visualizer/yarn.lock
    A package you depend on has a known security hole (CVE-2026-67214). 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
    visualizer/yarn.lock
    A package you depend on has a known security hole (GHSA-r28c-9q8g-f849). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-69153 postcss: PostCSS: Information disclosure via crafted sourceMappingURL
    visualizer/yarn.lock
    A package you depend on has a known security hole (CVE-2026-69153). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 4 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-28wg-ghj8-5hjv nanoid: non-secure generators can loop indefinitely with negative size
    /workdirs/scan-46435ce1-41de-4491-ac2b-4acacdbf03ec/visualizer/yarn.lock
    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-46435ce1-41de-4491-ac2b-4acacdbf03ec/visualizer/yarn.lock
    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-46435ce1-41de-4491-ac2b-4acacdbf03ec/visualizer/yarn.lock
    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-46435ce1-41de-4491-ac2b-4acacdbf03ec/visualizer/yarn.lock
    A package you depend on has a known security hole. 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.