gitsafehub
github.com/schollz/cowyo2 ↗

schollz/cowyo2

scanned 2026-08-15 · git a367ffc
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 dependencies✓Known OSS vulnerabilities10Risky 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ⓘ 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ⓘ 10 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-2v37-7h3g-55p8 nanoid: custom generators can loop indefinitely when size is zero
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/package-lock.json
    A package you depend on has a known security hole (CVE-2026-67213). Fix: Update that package to its patched version.
  • FYI GO-2026-5932 The golang.org/x/crypto/openpgp package is unmaintained, unsafe by design, and has known security issues
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GO-2026-5026 Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole (CVE-2026-39821). Fix: Update that package to its patched version.
  • FYI GO-2026-5942 Parsing an invalid SVCB or HTTPS RR can panic in golang.org/x/net/dns/dnsmessage
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole (CVE-2026-46600). Fix: Update that package to its patched version.
  • FYI GO-2026-5972 Enforce maximum recursion depth in encoding/asn1
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole (CVE-2026-33818). Fix: Update that package to its patched version.
  • FYI GO-2026-6088 Add recursion depth guard during decode in encoding/xml
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole (CVE-2026-56859). Fix: Update that package to its patched version.
  • FYI GO-2026-6089 Apply ReadHeaderTimeout when doing unencrypted HTTP/2 check in net/http
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole (CVE-2026-56853). Fix: Update that package to its patched version.
  • FYI GO-2026-6090 Limit handshake messages we are willing to accept post-handshake in crypto/tls
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole (CVE-2026-56862). Fix: Update that package to its patched version.
  • FYI GO-2026-6091 Fix Javascript regexp context tracking in html/template
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole (CVE-2026-56858). Fix: Update that package to its patched version.
  • FYI GO-2026-6218 Avoid quadratic complexity in resolvePath in net/url
    /workdirs/scan-12d208f9-8e6c-41f1-b04a-dac125a40b30/go.mod
    A package you depend on has a known security hole (CVE-2026-56860). 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ⓘ 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: 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.