github.com/sorafujitani/tsrepo ↗
sorafujitani/tsrepo
scanned 2026-08-13 · git 33a7fca
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional.
Re-check ↻
Informational scan, not a security audit. How this is computed .
🔑 Leaked secrets ✓ 📦 Vulnerable dependencies 2 🧬 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: sorafujitani
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 ⓘ
2 found
Packages you depend on that have known security holes (CVEs).
Worth fixing CVE-2026-4800 lodash: lodash: Arbitrary code execution via untrusted input in template imports
bun.lock
A package you depend on has a known security hole (CVE-2026-4800). Fix: Update that package to its patched version.
Worth fixing CVE-2026-2950 lodash: Lodash: Prototype pollution allows deletion of built-in prototype properties via array path bypass
bun.lock
A package you depend on has a known security hole (CVE-2026-2950). Fix: Update that package to its patched version.
via Trivy v0.70.0 · Apache-2.0
🧬 Known OSS vulnerabilities — OSV-Scanner ⓘ
4 found · 1 serious
Your dependencies cross-checked against the OSV vulnerability database.
Serious GHSA-3qcw-2rhx-2726 Turbo: Unexpected local code execution during Yarn Berry detection
/workdirs/scan-40370f5f-f053-4c66-a691-10adc1ca3a13/bun.lock
A package you depend on has a known security hole (CVE-2026-45772). Fix: Update that package to its patched version.
Worth fixing GHSA-f23m-r3pf-42rh lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
/workdirs/scan-40370f5f-f053-4c66-a691-10adc1ca3a13/bun.lock
A package you depend on has a known security hole (CVE-2025-13465). Fix: Update that package to its patched version.
Worth fixing GHSA-r5fr-rjxr-66jc lodash vulnerable to Code Injection via `_.template` imports key names
/workdirs/scan-40370f5f-f053-4c66-a691-10adc1ca3a13/bun.lock
A package you depend on has a known security hole (CVE-2021-23337). Fix: Update that package to its patched version.
Worth fixing GHSA-hcf7-66rw-9f5r Turbo: Login callback CSRF/session fixation
/workdirs/scan-40370f5f-f053-4c66-a691-10adc1ca3a13/bun.lock
A package you depend on has a known security hole (CVE-2026-45773). 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 ⓘ
none found ✓
Packages that look intentionally malicious: typosquats, sneaky install scripts.
Nothing found by this check. ✓
via Guarddog v2.10.0 · Apache-2.0
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.