gitsafehub
github.com/iomkarpanda/Traceflow ↗

iomkarpanda/Traceflow

scanned 2026-07-26 · git 2232b40
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 dependencies32Known OSS vulnerabilities37Risky 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ⓘ 32 found

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

  • Worth fixing GHSA-frvp-7c67-39w9 Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)
    frontend/package-lock.json
    A package you depend on has a known security hole (GHSA-frvp-7c67-39w9). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-14257 brace-expansion through 5.0.7 is vulnerable to denial of service via m ...
    frontend/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-0540 DOMPurify: DOMPurify: Cross-site scripting vulnerability
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-0540). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41238 DOMPurify: DOMPurify: Cross-Site Scripting bypass via prototype pollution
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41238). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41239 DOMPurify: Vue 2: DOMPurify: Cross-site scripting due to incomplete sanitization of template expressions
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41239). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41240 DOMPurify: DOMPurify: Cross-Site Scripting (XSS) via inconsistent tag sanitization
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41240). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-49458 dompurify: DOMPurify: Cross-site scripting due to improper sanitization of DOM nodes
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49458). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-49459 dompurify: DOMPurify: Cross-site scripting bypass allows arbitrary script execution
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49459). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-49978 dompurify: DOMPurify: Cross-site scripting vulnerability allows code execution
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49978). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-65898 DOMPurify before 3.4.11 fails to clone the ALLOWED_ATTR allowlist when ...
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65898). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-65902 DOMPurify before 3.4.7 (affected versions <= 3.4.5) passes direct refe ...
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65902). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-65903 DOMPurify before 3.4.0 contains a logic error in the ADD_TAGS function ...
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65903). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-65912 DOMPurify before 3.3.2 contains a URI validation bypass vulnerability ...
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65912). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-65913 DOMPurify before 3.3.2 contains a prototype pollution vulnerability in ...
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65913). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-65914 DOMPurify before 3.3.2 contains a mutation-XSS vulnerability when sani ...
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65914). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-16221 Impact: fast-uri versions from 2.3.1 through 4.1.0 (including the 3.x ...
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-16221). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64641 Next.js: Denial of Service in App Router using Server Actions
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64641). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64642 Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64642). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64645 Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64645). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64649 Next.js: Server-Side Request Forgery in Server Actions on custom servers
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64649). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64643 Next.js: Unauthenticated disclosure of internal Server Function endpoints
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64643). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64644 Next.js: Denial of Service in the Image Optimization API using SVGs
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64644). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64646 Next.js: Unbounded Server Action payload in Edge runtime
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64646). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64647 Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64647). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-64648 Next.js: Cache confusion of response bodies for requests with bodies
    frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64648). Fix: Update that package to its patched version.
… 7 more not shown

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 37 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing PYSEC-2026-1812 Pydantic regular expression denial of service
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/backend/requirements.txt
    A package you depend on has a known security hole (CVE-2024-3772). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1845 pytest has vulnerable tmpdir handling
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/backend/requirements.txt
    A package you depend on has a known security hole (CVE-2025-71176). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2270 python-dotenv reads key-value pairs from a .env file and can set them as environment variables. Prior to version 1.2.2, `set_key()` and `unset_key()` in python-dotenv follow symbolic links when rewrit
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/backend/requirements.txt
    A package you depend on has a known security hole (CVE-2026-28684). Fix: Update that package to its patched version.
  • Worth fixing GHSA-frvp-7c67-39w9 Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-mh99-v99m-4gvg brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/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-mh99-v99m-4gvg brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crash
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/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-39q2-94rc-95cp DOMPurify's ADD_TAGS function form bypasses FORBID_TAGS due to short-circuit evaluation
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65903). Fix: Update that package to its patched version.
  • Worth fixing GHSA-76mc-f452-cxcm DOMPurify: Hook mutation of `data.allowedTags` / `data.allowedAttributes` permanently pollutes `DEFAULT_ALLOWED_TAGS` / `DEFAULT_ALLOWED_ATTR`
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65902). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cj63-jhhr-wcxv DOMPurify USE_PROFILES prototype pollution allows event handlers
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65913). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cjmm-f4jc-qw8r DOMPurify ADD_ATTR predicate skips URI validation
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65912). Fix: Update that package to its patched version.
  • Worth fixing GHSA-cmwh-pvxp-8882 DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65898). Fix: Update that package to its patched version.
  • Worth fixing GHSA-crv5-9vww-q3g8 DOMPurify has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM mode
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41239). Fix: Update that package to its patched version.
  • Worth fixing GHSA-h7mw-gpvr-xq4m DOMPurify: FORBID_TAGS bypassed by function-based ADD_TAGS predicate (asymmetry with FORBID_ATTR fix)
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41240). Fix: Update that package to its patched version.
  • Worth fixing GHSA-h8r8-wccr-v5f2 DOMPurify is vulnerable to mutation-XSS via Re-Contextualization
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-65914). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hpcv-96wg-7vj8 DOMPurify: Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound `instanceof` checks
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49458). Fix: Update that package to its patched version.
  • Worth fixing GHSA-r47g-fvhr-h676 DOMPurify: IN_PLACE mode preserves attributes of a clobbered root element, allowing XSS via attacker-controlled root DOM
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49459). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rp9w-3fw7-7cwq DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside <template>.content
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-49978). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v2wj-7wpq-c8vv DOMPurify contains a Cross-site Scripting vulnerability
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-0540). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v9jr-rg53-9pgp DOMPurify: Prototype Pollution to XSS Bypass via CUSTOM_ELEMENT_HANDLING Fallback
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41238). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v2hh-gcrm-f6hx fast-uri vulnerable to host confusion via literal backslash authority delimiter
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-16221). Fix: Update that package to its patched version.
  • Worth fixing GHSA-4633-3j49-mh5q Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64647). Fix: Update that package to its patched version.
  • Worth fixing GHSA-4c39-4ccg-62r3 Next.js: Unbounded Server Action payload in Edge runtime
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64646). Fix: Update that package to its patched version.
  • Worth fixing GHSA-68g3-v927-f742 Next.js: Cache confusion of response bodies for requests with bodies
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64648). Fix: Update that package to its patched version.
  • Worth fixing GHSA-6gpp-xcg3-4w24 Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64642). Fix: Update that package to its patched version.
  • Worth fixing GHSA-89xv-2m56-2m9x Next.js: Server-Side Request Forgery in Server Actions on custom servers
    /workdirs/scan-bb781abe-ce57-48dd-a40b-3f18582b406b/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-64649). Fix: Update that package to its patched version.
… 12 more not shown

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.