gitsafehub
github.com/squat/prometheus-operator ↗

squat/prometheus-operator

scanned 2026-08-08 · git a24386e
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 secretsVulnerable dependencies3Known OSS vulnerabilities4Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks timed out

API keys, passwords or tokens committed into the repo.

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

via Gitleaks v8.21.2 · MIT

error: timeout after 120s

Vulnerable dependencies — Trivy 3 found

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

  • Worth fixing CVE-2021-22569 protobuf-java: potential DoS in the parsing procedure for binary data
    vendor/github.com/prometheus/client_model/pom.xml
    A package you depend on has a known security hole (CVE-2021-22569). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-7254 protobuf: StackOverflow vulnerability in Protocol Buffers
    vendor/github.com/prometheus/client_model/pom.xml
    A package you depend on has a known security hole (CVE-2024-7254). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-3171 protobuf-java: timeout in parser leads to DoS
    vendor/github.com/prometheus/client_model/pom.xml
    A package you depend on has a known security hole (CVE-2022-3171). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 4 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-735f-pc8j-v9w8 protobuf-java has potential Denial of Service issue
    /workdirs/scan-153ae50a-2ea5-4109-a279-bdb8e9486f86/vendor/github.com/prometheus/client_model/pom.xml
    A package you depend on has a known security hole (CVE-2024-7254). Fix: Update that package to its patched version.
  • Worth fixing GHSA-h4h5-3hr4-j3g2 protobuf-java has a potential Denial of Service issue
    /workdirs/scan-153ae50a-2ea5-4109-a279-bdb8e9486f86/vendor/github.com/prometheus/client_model/pom.xml
    A package you depend on has a known security hole (CVE-2022-3171). Fix: Update that package to its patched version.
  • Worth fixing GHSA-wrvw-hg22-4m67 A potential Denial of Service issue in protobuf-java
    /workdirs/scan-153ae50a-2ea5-4109-a279-bdb8e9486f86/vendor/github.com/prometheus/client_model/pom.xml
    A package you depend on has a known security hole (CVE-2021-22569). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-28484 An issue was discovered in the /api/connector endpoint handler in Yubico yubihsm-connector before 3.0.1 (in YubiHSM SDK before 2021.04). The handler did not validate the length of the request, which c
    /workdirs/scan-153ae50a-2ea5-4109-a279-bdb8e9486f86/vendor/golang.org
    A package you depend on has a known security hole (CVE-2021-28484). 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 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.