github.com/galderz/incus-spawn ↗
galderz/incus-spawn
scanned 2026-08-08 · git 9dd27de
2 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 3 📦 Vulnerable dependencies 4 🧬 Known OSS vulnerabilities — ⚠️ Risky code patterns ✓ ☠️ Malicious dependencies ✓ 🩺 Project health —
Chat with this repo
Simplify and Visualize This Repo
Self Host this repo
Check out more work of Developer: galderz
Security checks
🔑 Leaked secrets — Gitleaks ⓘ
3 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.
src/main/java/dev/incusspawn/proxy/CertificateAuthority.java:307
A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
src/main/java/dev/incusspawn/proxy/CertificateAuthority.java:51
A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
src/main/java/dev/incusspawn/proxy/CertificateAuthority.java:281
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 ⓘ
4 found
Packages you depend on that have known security holes (CVEs).
Worth fixing CVE-2026-54515 jackson-databind: jackson-databind: Ignored properties can be unexpectedly modified
pom.xml
A package you depend on has a known security hole (CVE-2026-54515). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59889 jackson-databind: @JsonView bypassed for @JsonUnwrapped container properties on deserialization
pom.xml
A package you depend on has a known security hole (CVE-2026-59889). Fix: Update that package to its patched version.
Worth fixing CVE-2026-55851 io.netty/netty-codec-haproxy: Netty codec-haproxy: Denial of Service via crafted PROXY protocol v2 message
pom.xml
A package you depend on has a known security hole (CVE-2026-55851). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59919 io.netty/netty-codec-haproxy: Netty: Improper CR/LF neutralization in netty-codec-haproxy
pom.xml
A package you depend on has a known security hole (CVE-2026-59919). 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.