github.com/smellslikeml/hitl_adaptive_active_learning_lithium ↗

smellslikeml/hitl_adaptive_active_learning_lithium

scanned 2026-08-12 · git 4dcc49f

1 of 6 checks flagged a security issue

🟡 Worth a look

Only 3 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets✓Vulnerable dependencies8Known OSS vulnerabilities—Risky 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ⓘ 8 found

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

Worth fixing CVE-2024-21503 psf/black: ReDoS via the lines_with_leading_tabs_expanded() function in strings.py file

requirements.txt

A package you depend on has a known security hole (CVE-2024-21503). Fix: Update that package to its patched version.
Worth fixing CVE-2024-22421 JupyterLab is an extensible environment for interactive and reproducib ...

requirements.txt

A package you depend on has a known security hole (CVE-2024-22421). Fix: Update that package to its patched version.
Worth fixing CVE-2024-43805 jupyterlab is an extensible environment for interactive and reproducib ...

requirements.txt

A package you depend on has a known security hole (CVE-2024-43805). Fix: Update that package to its patched version.
Worth fixing CVE-2026-40171 Jupyter Notebook: JupyterLab: @jupyter-notebook/help-extension: @jupyterlab/help-extension: Jupyter Notebook and JupyterLab: Session takeover via stored cross-site scripting

requirements.txt

A package you depend on has a known security hole (CVE-2026-40171). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42557 jupyterlab: JupyterLab: Arbitrary code execution via deceptive button in HTML output

requirements.txt

A package you depend on has a known security hole (CVE-2026-42557). Fix: Update that package to its patched version.
Worth fixing CVE-2024-22420 JupyterLab is an extensible environment for interactive and reproducib ...

requirements.txt

A package you depend on has a known security hole (CVE-2024-22420). Fix: Update that package to its patched version.
Worth fixing CVE-2025-71176 pytest: pytest: Denial of Service or Privilege Escalation via insecure temporary directory handling

requirements.txt

A package you depend on has a known security hole (CVE-2025-71176). Fix: Update that package to its patched version.
Minor CVE-2024-34062 python-tqdm: non-boolean CLI arguments may lead to local code execution

requirements.txt

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

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ timed out

Your dependencies cross-checked against the OSV vulnerability database.

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

via OSV-Scanner v1.9.2 · Apache-2.0

error: timeout after 400s

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ⓘ timed out

Packages that look intentionally malicious: typosquats, sneaky install scripts.

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

via Guarddog v2.10.0 · Apache-2.0

error: pypi:timeout

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.