bloomberg/bde

scanned 2026-08-14 · git 488015c

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 vulnerabilities3Risky code patterns✓Malicious dependencies✓Project 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ⓘ 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ⓘ 3 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing CVE-2025-58050 PCRE2: heap-buffer-overflow read in match_ref due to missing boundary restoration in SCS

/workdirs/scan-b25dea80-9f5c-4a18-bf57-c9cde74ec24a/thirdparty/pcre2

A package you depend on has a known security hole (CVE-2025-58050). Fix: Update that package to its patched version.
FYI OSV-2025-300 Negative-size-param in recurse_update_offsets

/workdirs/scan-b25dea80-9f5c-4a18-bf57-c9cde74ec24a/thirdparty/pcre2

A package you depend on has a known security hole. Fix: Update that package to its patched version.
FYI OSV-2026-343 Heap-buffer-overflow in pcre2_compile_32

/workdirs/scan-b25dea80-9f5c-4a18-bf57-c9cde74ec24a/thirdparty/pcre2

A package you depend on has a known security hole. 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.