gitsafehub
github.com/sphireinc/foundry ↗

sphireinc/foundry

scanned 2026-07-23 · git 832d343
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 secrets5Vulnerable dependencies✓Known OSS vulnerabilities✓Risky code patterns✓Malicious dependencies—Project health—

Security checks

Leaked secrets — Gitleaksⓘ 5 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.
    .env.example:6
    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.
    .env.example:6
    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.
    data/admin/locks.yaml:6
    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.
    internal/commands/doctor/doctor.go:182
    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.
    docs/coverage/index.html:14478
    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ⓘ 40 found

Your dependencies cross-checked against the OSV vulnerability database.

  • FYI GO-2026-5932 The golang.org/x/crypto/openpgp package is unmaintained, unsafe by design, and has known security issues
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GO-2025-3955 CrossOriginProtection insecure bypass patterns not limited to exact matches in net/http
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-47910). Fix: Update that package to its patched version.
  • FYI GO-2025-4006 Excessive CPU consumption in ParseAddress in net/mail
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-61725). Fix: Update that package to its patched version.
  • FYI GO-2025-4007 Quadratic complexity when checking name constraints in crypto/x509
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-58187). Fix: Update that package to its patched version.
  • FYI GO-2025-4008 ALPN negotiation error contains attacker controlled information in crypto/tls
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-58189). Fix: Update that package to its patched version.
  • FYI GO-2025-4009 Quadratic complexity when parsing some invalid inputs in encoding/pem
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-61723). Fix: Update that package to its patched version.
  • FYI GO-2025-4010 Insufficient validation of bracketed IPv6 hostnames in net/url
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-47912). Fix: Update that package to its patched version.
  • FYI GO-2025-4011 Parsing DER payload can cause memory exhaustion in encoding/asn1
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-58185). Fix: Update that package to its patched version.
  • FYI GO-2025-4012 Lack of limit when parsing cookies can cause memory exhaustion in net/http
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-58186). Fix: Update that package to its patched version.
  • FYI GO-2025-4013 Panic when validating certificates with DSA public keys in crypto/x509
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-58188). Fix: Update that package to its patched version.
  • FYI GO-2025-4014 Unbounded allocation when parsing GNU sparse map in archive/tar
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-58183). Fix: Update that package to its patched version.
  • FYI GO-2025-4015 Excessive CPU consumption in Reader.ReadResponse in net/textproto
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-61724). Fix: Update that package to its patched version.
  • FYI GO-2025-4155 Excessive resource consumption when printing error string for host certificate validation in crypto/x509
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-61729). Fix: Update that package to its patched version.
  • FYI GO-2025-4175 Improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-61727). Fix: Update that package to its patched version.
  • FYI GO-2026-4337 Unexpected session resumption in crypto/tls
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-68121). Fix: Update that package to its patched version.
  • FYI GO-2026-4340 Handshake messages may be processed at the incorrect encryption level in crypto/tls
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-61730). Fix: Update that package to its patched version.
  • FYI GO-2026-4341 Memory exhaustion in query parameter parsing in net/url
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-61726). Fix: Update that package to its patched version.
  • FYI GO-2026-4342 Excessive CPU consumption when building archive index in archive/zip
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2025-61728). Fix: Update that package to its patched version.
  • FYI GO-2026-4601 Incorrect parsing of IPv6 host literals in net/url
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2026-25679). Fix: Update that package to its patched version.
  • FYI GO-2026-4602 FileInfo can escape from a Root in os
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2026-27139). Fix: Update that package to its patched version.
  • FYI GO-2026-4603 URLs in meta content attribute actions are not escaped in html/template
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2026-27142). Fix: Update that package to its patched version.
  • FYI GO-2026-4864 TOCTOU permits root escape on Linux via Root.Chmod in os in internal/syscall/unix
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2026-32282). Fix: Update that package to its patched version.
  • FYI GO-2026-4865 JsBraceDepth Context Tracking Bugs (XSS) in html/template
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2026-32289). Fix: Update that package to its patched version.
  • FYI GO-2026-4869 Unbounded allocation for old GNU sparse in archive/tar
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2026-32288). Fix: Update that package to its patched version.
  • FYI GO-2026-4870 Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls
    /workdirs/scan-87f6d251-7c4a-4158-9119-7d1327b23847/go.mod
    A package you depend on has a known security hole (CVE-2026-32283). Fix: Update that package to its patched version.
… 15 more not shown

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ⓘ timed out

Packages that look intentionally malicious: typosquats, sneaky install scripts.

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

via Guarddog v2.10.0 · Apache-2.0

error: npm:timeout; go:timeout

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.