github.com/kolibril13/ipy-react-three-fiber ↗
kolibril13/ipy-react-three-fiber
scanned 2026-08-12 · git 6738891
2 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 dependencies 3 🧬 Known OSS vulnerabilities 4 ⚠️ 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: kolibril13
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 ⓘ
3 found
Packages you depend on that have known security holes (CVEs).
Worth fixing CVE-2025-27789 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups
package-lock.json
A package you depend on has a known security hole (CVE-2025-27789). Fix: Update that package to its patched version.
Worth fixing CVE-2024-21538 cross-spawn: regular expression denial of service
package-lock.json
A package you depend on has a known security hole (CVE-2024-21538). Fix: Update that package to its patched version.
Worth fixing GHSA-67mh-4wv8-2f99 esbuild enables any website to send any requests to the development server and read the response
package-lock.json
A package you depend on has a known security hole (GHSA-67mh-4wv8-2f99). Fix: Update that package to its patched version.
via Trivy v0.70.0 · Apache-2.0
🧬 Known OSS vulnerabilities — OSV-Scanner ⓘ
4 found
Your dependencies cross-checked against the OSV vulnerability database.
Worth fixing GHSA-968p-4wvh-cqc8 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups
/workdirs/scan-55a389e1-2ac0-4bdf-830a-1b599031a423/package-lock.json
A package you depend on has a known security hole (CVE-2025-27789). Fix: Update that package to its patched version.
Worth fixing GHSA-3xgq-45jj-v275 Regular Expression Denial of Service (ReDoS) in cross-spawn
/workdirs/scan-55a389e1-2ac0-4bdf-830a-1b599031a423/package-lock.json
A package you depend on has a known security hole (CVE-2024-21538). Fix: Update that package to its patched version.
Worth fixing GHSA-67mh-4wv8-2f99 esbuild enables any website to send any requests to the development server and read the response
/workdirs/scan-55a389e1-2ac0-4bdf-830a-1b599031a423/package-lock.json
A package you depend on has a known security hole. Fix: Update that package to its patched version.
Worth fixing GHSA-p6mc-m468-83gw Prototype Pollution in lodash
/workdirs/scan-55a389e1-2ac0-4bdf-830a-1b599031a423/package-lock.json
A package you depend on has a known security hole (CVE-2020-8203). 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 ⓘ
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: npm: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.