gitsafehub
github.com/tino097/ckanext-meerbusch ↗

tino097/ckanext-meerbusch

scanned 2026-08-11 · git ba77568
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 secretsVulnerable dependencies4Known OSS vulnerabilities6Risky code patternsMalicious dependenciesProject 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 4 found

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

  • Worth fixing CVE-2021-46823 python-ldap: Regular expression denial of service in LDAP schema parser
    requirements.txt
    A package you depend on has a known security hole (CVE-2021-46823). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-61911 python-ldap: sanitization bypass in ldap.filter.escape_filter_chars
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-61911). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-61912 python-ldap: python-ldap Vulnerable to Improper Encoding or Escaping of Output and Improper Null Termination
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-61912). Fix: Update that package to its patched version.
  • Worth fixing GHSA-r8wq-qrxc-hmcm ReDoS in LDAP schema parser
    requirements.txt
    A package you depend on has a known security hole (GHSA-r8wq-qrxc-hmcm). 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-2026-1846 python-ldap is Vulnerable to Improper Encoding or Escaping of Output and Improper Null Termination
    /workdirs/scan-9347d4ef-17e3-4dc6-a5d0-ff9be78fa60e/dev-requirements.txt
    A package you depend on has a known security hole (CVE-2025-61912). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1847 python-ldap has sanitization bypass in ldap.filter.escape_filter_chars
    /workdirs/scan-9347d4ef-17e3-4dc6-a5d0-ff9be78fa60e/dev-requirements.txt
    A package you depend on has a known security hole (CVE-2025-61911). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-912 Denial of Service in python-ldap
    /workdirs/scan-9347d4ef-17e3-4dc6-a5d0-ff9be78fa60e/dev-requirements.txt
    A package you depend on has a known security hole (CVE-2021-46823). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1846 python-ldap is Vulnerable to Improper Encoding or Escaping of Output and Improper Null Termination
    /workdirs/scan-9347d4ef-17e3-4dc6-a5d0-ff9be78fa60e/requirements.txt
    A package you depend on has a known security hole (CVE-2025-61912). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1847 python-ldap has sanitization bypass in ldap.filter.escape_filter_chars
    /workdirs/scan-9347d4ef-17e3-4dc6-a5d0-ff9be78fa60e/requirements.txt
    A package you depend on has a known security hole (CVE-2025-61911). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-912 Denial of Service in python-ldap
    /workdirs/scan-9347d4ef-17e3-4dc6-a5d0-ff9be78fa60e/requirements.txt
    A package you depend on has a known security hole (CVE-2021-46823). 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.