github.com/msaleemdev/react-todo-context ↗

msaleemdev/react-todo-context

scanned 2026-07-17 · git 50ee6b0

2 of 6 checks flagged a security issue

🟡 Worth a look

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 dependencies2Known OSS vulnerabilities3Risky code patterns✓Malicious dependencies—Project health10

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-53571 vite: `server.fs.deny` bypass on Windows alternate paths

package-lock.json

A package you depend on has a known security hole (CVE-2026-53571). Fix: Update that package to its patched version.
Worth fixing CVE-2026-53632 launch-editor: launch-editor: Credential compromise via NTLMv2 password hash leak through UNC path access

package-lock.json

A package you depend on has a known security hole (CVE-2026-53632). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 3 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GHSA-fx2h-pf6j-xcff vite: `server.fs.deny` bypass on Windows alternate paths

/workdirs/scan-e28ea185-7432-40b5-89c2-a33abccd7a6a/package-lock.json

A package you depend on has a known security hole (CVE-2026-53571). Fix: Update that package to its patched version.
Worth fixing GHSA-v6wh-96g9-6wx3 launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows

/workdirs/scan-e28ea185-7432-40b5-89c2-a33abccd7a6a/package-lock.json

A package you depend on has a known security hole (CVE-2026-53632). Fix: Update that package to its patched version.
Minor GHSA-4x5r-pxfx-6jf8 @babel/core: Arbitrary File Read via sourceMappingURL Comment

/workdirs/scan-e28ea185-7432-40b5-89c2-a33abccd7a6a/package-lock.json

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

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

Worth fixing scorecard-overall OpenSSF Scorecard overall: 1.4/10

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-CII-Best-Practices CII-Best-Practices scored 0: no effort to earn an OpenSSF best practices badge detected

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Code-Review Code-Review scored 0: Found 0/2 approved changesets -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Contributors Contributors scored 0: project has 0 contributing companies or organizations -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Dependency-Update-Tool Dependency-Update-Tool scored 0: no update tool detected

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Fuzzing Fuzzing scored 0: project is not fuzzed

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-License License scored 0: license file not detected

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Maintained Maintained scored 0: project was created within the last 90 days. Please review its contents carefully

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-SAST SAST scored 0: no SAST tool detected

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Security-Policy Security-Policy scored 0: security policy file not detected

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.

via OpenSSF Scorecard v5.5.0 · 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.