github.com/ronghanghu/mesh-transformer-jax ↗

ronghanghu/mesh-transformer-jax

scanned 2026-08-13 · git 0a75ca9

1 of 6 checks flagged a security issue

🔴 Needs attention

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 · 4 serious

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

Serious CVE-2023-6019 ray: Ray Dashboard Command Injection

requirements.txt

A package you depend on has a known security hole (CVE-2023-6019). Fix: Update that package to its patched version.
Serious CVE-2023-6020 Ray Missing Authorization vulnerability

requirements.txt

A package you depend on has a known security hole (CVE-2023-6020). Fix: Update that package to its patched version.
Serious CVE-2023-6021 Ray Path Traversal vulnerability

requirements.txt

A package you depend on has a known security hole (CVE-2023-6021). Fix: Update that package to its patched version.
Serious CVE-2025-62593 ray: Ray is vulnerable to RCE via Safari & Firefox Browsers through DNS Rebinding Attack

requirements.txt

A package you depend on has a known security hole (CVE-2025-62593). Fix: Update that package to its patched version.
Worth fixing CVE-2026-32981 ray: Ray Dashboard Path Traversal Leading to Local File Disclosure

requirements.txt

A package you depend on has a known security hole (CVE-2026-32981). Fix: Update that package to its patched version.
Worth fixing CVE-2026-57516 ray: Ray: Remote code execution via unsafe deserialization in WebDataset reader

requirements.txt

A package you depend on has a known security hole (CVE-2026-57516). Fix: Update that package to its patched version.
Worth fixing CVE-2025-1979 ray: Insertion of Sensitive Information into Log File

requirements.txt

A package you depend on has a known security hole (CVE-2025-1979). Fix: Update that package to its patched version.
Worth fixing CVE-2026-27482 Ray dashboard DELETE endpoints allow unauthenticated browser-triggered DoS (Serve shutdown / job deletion)

requirements.txt

A package you depend on has a known security hole (CVE-2026-27482). 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.