github.com/superclaude-org/supergemini_framework ↗

superclaude-org/supergemini_framework

scanned 2026-08-12 · git b19a1c1

1 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 dependencies8Known OSS vulnerabilities✓Risky 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ⓘ 8 found

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

Worth fixing CVE-2026-32274 black: Black: Arbitrary file writes from unsanitized user input in cache file name

uv.lock

A package you depend on has a known security hole (CVE-2026-32274). Fix: Update that package to its patched version.
Worth fixing CVE-2026-32274 black: Black: Arbitrary file writes from unsanitized user input in cache file name

uv.lock

A package you depend on has a known security hole (CVE-2026-32274). Fix: Update that package to its patched version.
Worth fixing CVE-2025-71176 pytest: pytest: Denial of Service or Privilege Escalation via insecure temporary directory handling

uv.lock

A package you depend on has a known security hole (CVE-2025-71176). Fix: Update that package to its patched version.
Worth fixing CVE-2025-71176 pytest: pytest: Denial of Service or Privilege Escalation via insecure temporary directory handling

uv.lock

A package you depend on has a known security hole (CVE-2025-71176). Fix: Update that package to its patched version.
Worth fixing CVE-2025-47273 setuptools: Path Traversal Vulnerability in setuptools PackageIndex

uv.lock

A package you depend on has a known security hole (CVE-2025-47273). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59890 setuptools: setuptools: MANIFEST.in exclusion bypass in sdist via Unicode normalization collision (NFC/NFD)

uv.lock

A package you depend on has a known security hole (CVE-2026-59890). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59890 setuptools: setuptools: MANIFEST.in exclusion bypass in sdist via Unicode normalization collision (NFC/NFD)

uv.lock

A package you depend on has a known security hole (CVE-2026-59890). Fix: Update that package to its patched version.
Minor CVE-2026-4539 pygments: Pygments: Denial of Service via inefficient regular expression processing in AdlLexer

uv.lock

A package you depend on has a known security hole (CVE-2026-4539). 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.