github.com/apaszke/jax ↗
apaszke/jax
scanned 2026-08-06 · git a3997ba
1 of 6 checks flagged a security issue
🟡 Worth a look
Only 2 of 6 checks finished — treat this as provisional.
Re-check ↻
Informational scan, not a security audit. How this is computed .
🔑 Leaked secrets — 📦 Vulnerable dependencies 4 🧬 Known OSS vulnerabilities — ⚠️ Risky code patterns ✓ ☠️ Malicious dependencies — 🩺 Project health —
Chat with this repo
Simplify and Visualize This Repo
Self Host this repo
Check out more work of Developer: apaszke
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 400s
📦 Vulnerable dependencies — Trivy ⓘ
4 found
Packages you depend on that have known security holes (CVEs).
Worth fixing CVE-2021-20270 python-pygments: Infinite loop in SML lexer may lead to DoS
docs/requirements.txt
A package you depend on has a known security hole (CVE-2021-20270). Fix: Update that package to its patched version.
Worth fixing CVE-2021-27291 python-pygments: ReDoS in multiple lexers
docs/requirements.txt
A package you depend on has a known security hole (CVE-2021-27291). Fix: Update that package to its patched version.
Worth fixing CVE-2022-40896 pygments: ReDoS in pygments
docs/requirements.txt
A package you depend on has a known security hole (CVE-2022-40896). Fix: Update that package to its patched version.
Minor CVE-2026-4539 pygments: Pygments: Denial of Service via inefficient regular expression processing in AdlLexer
docs/requirements.txt
A package you depend on has a known security hole (CVE-2026-4539). 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.