srivatsn/sanskrit-daily

scanned 2026-08-09 · git 8acef05

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 dependencies4Known OSS vulnerabilities5Risky 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ⓘ 4 found

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

Worth fixing CVE-2026-4867 path-to-regexp: path-to-regexp: Denial of Service via catastrophic backtracking from malformed URL parameters

package-lock.json

A package you depend on has a known security hole (CVE-2026-4867). Fix: Update that package to its patched version.
Worth fixing CVE-2026-8723 ### Summary `qs.stringify` throws `TypeError` when called with `arr ...

package-lock.json

A package you depend on has a known security hole (CVE-2026-8723). Fix: Update that package to its patched version.
Minor CVE-2026-12590 body-parser: body-parser: Denial of Service via invalid limit option

package-lock.json

A package you depend on has a known security hole (CVE-2026-12590). Fix: Update that package to its patched version.
Minor CVE-2026-2391 qs: qs's arrayLimit bypass in comma parsing allows denial of service

package-lock.json

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

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 5 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GHSA-37ch-88jc-xwx2 path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters

/workdirs/scan-ec2b345b-df9b-434e-aaba-18bf687177f0/package-lock.json

A package you depend on has a known security hole (CVE-2024-45296). Fix: Update that package to its patched version.
Worth fixing GHSA-q8mj-m7cp-5q26 qs has a remotely triggerable DoS: qs.stringify crashes with TypeError on null/undefined entries in comma-format arrays when encodeValuesOnly is set

/workdirs/scan-ec2b345b-df9b-434e-aaba-18bf687177f0/package-lock.json

A package you depend on has a known security hole (CVE-2026-8723). Fix: Update that package to its patched version.
Minor GHSA-v422-hmwv-36x6 body-parser vulnerable to denial of service when invalid limit value silently disables size enforcement

/workdirs/scan-ec2b345b-df9b-434e-aaba-18bf687177f0/package-lock.json

A package you depend on has a known security hole (CVE-2026-12590). Fix: Update that package to its patched version.
Minor GHSA-g7r4-m6w7-qqqr esbuild allows arbitrary file read when running the development server on Windows

/workdirs/scan-ec2b345b-df9b-434e-aaba-18bf687177f0/package-lock.json

A package you depend on has a known security hole. Fix: Update that package to its patched version.
Minor GHSA-w7fw-mjwx-w883 qs's arrayLimit bypass in comma parsing allows denial of service

/workdirs/scan-ec2b345b-df9b-434e-aaba-18bf687177f0/package-lock.json

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