gitsafehub
github.com/sungam3r/rabbitmq-website ↗

sungam3r/rabbitmq-website

scanned 2026-08-11 · git d22cfb9
3 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets10Vulnerable dependencies6Known OSS vulnerabilities6Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks 10 found · 10 serious

API keys, passwords or tokens committed into the repo.

  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/definitions.md:88
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/monitoring.md:545
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/monitoring.md:581
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/memory-use.md:323
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/memory-use.md:362
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/memory-use.md:589
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/shovel-dynamic.md:206
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/shovel-dynamic.md:258
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/vhosts.md:84
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
    site/vhosts.md:128
    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 6 found

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

  • Worth fixing CVE-2026-41066 lxml: python: lxml: Information disclosure via untrusted XML input leading to local file read
    Pipfile.lock
    A package you depend on has a known security hole (CVE-2026-41066). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-27783 python-lxml: mXSS due to the use of improper parser
    Pipfile.lock
    A package you depend on has a known security hole (CVE-2020-27783). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-28957 python-lxml: Missing input sanitization for formaction HTML5 attributes may lead to XSS
    Pipfile.lock
    A package you depend on has a known security hole (CVE-2021-28957). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-43818 python-lxml: HTML Cleaner allows crafted and SVG embedded scripts to pass through
    Pipfile.lock
    A package you depend on has a known security hole (CVE-2021-43818). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-2309 lxml: NULL Pointer Dereference in lxml
    Pipfile.lock
    A package you depend on has a known security hole (CVE-2022-2309). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-69534 python-markdown: denial of service via malformed HTML-like sequences
    Pipfile.lock
    A package you depend on has a known security hole (CVE-2025-69534). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 6 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing PYSEC-2020-62 A XSS vulnerability was discovered in python-lxml's clean module. The module's parser didn't properly imitate browsers, which caused different behaviors between the sanitizer and the user's page. A re
    /workdirs/scan-aee7f55f-3dcd-42a8-a9d1-bd2a124a0860/Pipfile.lock
    A package you depend on has a known security hole (CVE-2020-27783). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2021-19 An XSS vulnerability was discovered in python-lxml's clean module versions before 4.6.3. When disabling the safe_attrs_only and forms arguments, the Cleaner class does not remove the formaction attrib
    /workdirs/scan-aee7f55f-3dcd-42a8-a9d1-bd2a124a0860/Pipfile.lock
    A package you depend on has a known security hole (CVE-2021-28957). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2021-852 lxml is a library for processing XML and HTML in the Python language. Prior to version 4.6.5, the HTML Cleaner in lxml.html lets certain crafted script content pass through, as well as script content
    /workdirs/scan-aee7f55f-3dcd-42a8-a9d1-bd2a124a0860/Pipfile.lock
    A package you depend on has a known security hole (CVE-2021-43818). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2022-230 NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlie
    /workdirs/scan-aee7f55f-3dcd-42a8-a9d1-bd2a124a0860/Pipfile.lock
    A package you depend on has a known security hole (CVE-2022-2309). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-87 lxml is a library for processing XML and HTML in the Python language. Prior to 6.1.0, using either of the two parsers in the default configuration (with resolve_entities=True) allows untrusted XML inp
    /workdirs/scan-aee7f55f-3dcd-42a8-a9d1-bd2a124a0860/Pipfile.lock
    A package you depend on has a known security hole (CVE-2026-41066). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-89 Python-Markdown version 3.8 contain a vulnerability where malformed HTML-like sequences can cause html.parser.HTMLParser to raise an unhandled AssertionError during Markdown parsing. Because Python-Ma
    /workdirs/scan-aee7f55f-3dcd-42a8-a9d1-bd2a124a0860/Pipfile.lock
    A package you depend on has a known security hole (CVE-2025-69534). 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.