github.com/mikewang817/TFormula ↗
mikewang817/TFormula
scanned 2026-08-05 · git 9dbf014
2 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 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: mikewang817
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 ⓘ
3 found
Packages you depend on that have known security holes (CVEs).
Worth fixing CVE-2026-14257 brace-expansion: Brace-expansion: Denial of Service via memory exhaustion in expand() function
package-lock.json
A package you depend on has a known security hole (CVE-2026-14257). Fix: Update that package to its patched version.
Worth fixing CVE-2026-69152 brace-expansion: brace-expansion: Denial of Service via unbounded intermediate arrays
package-lock.json
A package you depend on has a known security hole (CVE-2026-69152). Fix: Update that package to its patched version.
Worth fixing GHSA-f88m-g3jw-g9cj sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591
package-lock.json
A package you depend on has a known security hole (GHSA-f88m-g3jw-g9cj). 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-mh99-v99m-4gvg brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash
/workdirs/scan-f6205b29-7864-4634-8e82-991ade7785a5/package-lock.json
A package you depend on has a known security hole (CVE-2026-14257). Fix: Update that package to its patched version.
Worth fixing GHSA-rgw5-rvv9-x895 brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation
/workdirs/scan-f6205b29-7864-4634-8e82-991ade7785a5/package-lock.json
A package you depend on has a known security hole (CVE-2026-69152). Fix: Update that package to its patched version.
Worth fixing GHSA-fxqj-rqcc-2cmp PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset
/workdirs/scan-f6205b29-7864-4634-8e82-991ade7785a5/package-lock.json
A package you depend on has a known security hole (CVE-2026-69153). Fix: Update that package to its patched version.
Worth fixing GHSA-f88m-g3jw-g9cj sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591
/workdirs/scan-f6205b29-7864-4634-8e82-991ade7785a5/package-lock.json
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 ⓘ
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.