gobuffalo/lush

scanned 2026-08-06 · git 6ae0033

2 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 dependencies1Known OSS vulnerabilities125Risky 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ⓘ 1 found

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

Worth fixing CVE-2022-28948 golang-gopkg-yaml: crash when attempting to deserialize invalid input

go.mod

A package you depend on has a known security hole (CVE-2022-28948). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 125 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GO-2022-0603 Panic in gopkg.in/yaml.v3

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.sum

A package you depend on has a known security hole (CVE-2022-28948). Fix: Update that package to its patched version.
FYI GO-2021-0226 Cross-site scripting in net/http/cgi and net/http/fcgi

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2020-24553). Fix: Update that package to its patched version.
FYI GO-2021-0234 Infinite loop when decoding inputs in encoding/xml

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-27918). Fix: Update that package to its patched version.
FYI GO-2021-0235 Incorrect operations on the P-224 curve in crypto/elliptic

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-3114). Fix: Update that package to its patched version.
FYI GO-2021-0239 Improper sanitization when resolving values from DNS in net

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-33195). Fix: Update that package to its patched version.
FYI GO-2021-0240 Panic when reading certain archives in archive/zip

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-33196). Fix: Update that package to its patched version.
FYI GO-2021-0241 Attacker can drop certain headers in net/http/httputil

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-33197). Fix: Update that package to its patched version.
FYI GO-2021-0242 Panic on inputs with large exponents in math/big

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-33198). Fix: Update that package to its patched version.
FYI GO-2021-0243 Panic on certain certificates in crypto/tls

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-34558). Fix: Update that package to its patched version.
FYI GO-2021-0245 Panic in ReverseProxy in net/http/httputil

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-36221). Fix: Update that package to its patched version.
FYI GO-2021-0263 Panic on invalid symbol tables in debug/macho

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-41771). Fix: Update that package to its patched version.
FYI GO-2021-0264 Panic when opening certain archives in archive/zip

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-41772). Fix: Update that package to its patched version.
FYI GO-2021-0317 Uncontrolled memory consumption in math/big

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-23772). Fix: Update that package to its patched version.
FYI GO-2021-0319 Incorrect computation for some invalid field elements in crypto/elliptic

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-23806). Fix: Update that package to its patched version.
FYI GO-2021-0347 Stack exhaustion when compiling deeply nested expressions in regexp

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-24921). Fix: Update that package to its patched version.
FYI GO-2022-0236 Panic due to large headers in net/http and golang.org/x/net/http/httpguts

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-31525). Fix: Update that package to its patched version.
FYI GO-2022-0273 Panic due to crafted inputs in archive/zip

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-39293). Fix: Update that package to its patched version.
FYI GO-2022-0288 Unbounded memory growth in net/http and golang.org/x/net/http2

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-44716). Fix: Update that package to its patched version.
FYI GO-2022-0289 Misdirected I/O in syscall

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2021-44717). Fix: Update that package to its patched version.
FYI GO-2022-0433 Stack overflow from a large amount of PEM data in encoding/pem

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-24675). Fix: Update that package to its patched version.
FYI GO-2022-0435 Panic due to large inputs affecting P-256 curves in crypto/elliptic

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-28327). Fix: Update that package to its patched version.
FYI GO-2022-0477 Indefinite hang with large buffers on Windows in crypto/rand

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-30634). Fix: Update that package to its patched version.
FYI GO-2022-0493 Incorrect privilege reporting in syscall and golang.org/x/sys/unix

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-29526). Fix: Update that package to its patched version.
FYI GO-2022-0515 Stack exhaustion due to deeply nested types in go/parser

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-1962). Fix: Update that package to its patched version.
FYI GO-2022-0520 Exposure of client IP addresses in net/http

/workdirs/scan-f4cbdc2d-60ee-48cc-b442-3795979776e3/go.mod

A package you depend on has a known security hole (CVE-2022-32148). Fix: Update that package to its patched version.

… 100 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ⓘ 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.