DanMat/Divvy

scanned 2026-07-25 · git 139bc8c

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 dependencies9Known 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ⓘ 9 found

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

Worth fixing GHSA-2f96-g7mh-g2hx GitPython: Command Injection via git long-option prefix abbreviation bypass of CVE-2026-42215 blocklist

uv.lock

A package you depend on has a known security hole (GHSA-2f96-g7mh-g2hx). Fix: Update that package to its patched version.
Worth fixing GHSA-3rp5-jjmw-4wv2 GitPython: git-config section-name injection enables arbitrary config directives (core.sshCommand RCE)

uv.lock

A package you depend on has a known security hole (GHSA-3rp5-jjmw-4wv2). Fix: Update that package to its patched version.
Worth fixing GHSA-6p8h-3wgx-97gf GitPython: Incomplete unsafe_git_clone_options denylist omits --template enabling arbitrary command execution via clone hooks

uv.lock

A package you depend on has a known security hole (GHSA-6p8h-3wgx-97gf). Fix: Update that package to its patched version.
Worth fixing GHSA-94p4-4cq8-9g67 GitPython: Environment-variable exfiltration via Repo.create_remote() / Remote.add() URL (incomplete fix of GHSA-rwj8-pgh3-r573)

uv.lock

A package you depend on has a known security hole (GHSA-94p4-4cq8-9g67). Fix: Update that package to its patched version.
Worth fixing GHSA-956x-8gvw-wg5v GitPython: command injection via unguarded Git options in `Repo.archive()`, `git.ls_remote()`, and arbitrary file overwrite via `Repo.iter_commits()` / `Repo.blame()`

uv.lock

A package you depend on has a known security hole (GHSA-956x-8gvw-wg5v). Fix: Update that package to its patched version.
Worth fixing GHSA-fjr4-x663-mwxc GitPython: Arbitrary file overwrite via git diff --output argument injection in Diffable.diff (key- and value-controlled)

uv.lock

A package you depend on has a known security hole (GHSA-fjr4-x663-mwxc). Fix: Update that package to its patched version.
Worth fixing GHSA-r9mr-m37c-5fr3 GitPython: Unsafe git option guard bypass via single-character kwarg value token smuggling enables arbitrary command execution

uv.lock

A package you depend on has a known security hole (GHSA-r9mr-m37c-5fr3). Fix: Update that package to its patched version.
Worth fixing GHSA-rwj8-pgh3-r573 GitPython: Environment-variable exfiltration via os.path.expandvars() on Repo.clone_from() URL

uv.lock

A package you depend on has a known security hole (GHSA-rwj8-pgh3-r573). Fix: Update that package to its patched version.
Worth fixing GHSA-v396-v7q4-x2qj GitPython unsafe clone option gate bypass through joined short options

uv.lock

A package you depend on has a known security hole (GHSA-v396-v7q4-x2qj). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ timed out

Your dependencies cross-checked against the OSV vulnerability database.

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

via OSV-Scanner v1.9.2 · Apache-2.0

error: timeout after 120s

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.