kaelwd/netflix-dispatch

scanned 2026-08-13 · git 7e98dde

1 of 6 checks flagged a security issue

🔴 Needs attention

Only 3 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets✓Vulnerable dependencies228Known OSS vulnerabilities—Risky 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ⓘ 228 found · 4 serious

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

Serious CVE-2023-45133 babel: arbitrary code execution

docs/package-lock.json

A package you depend on has a known security hole (CVE-2023-45133). Fix: Update that package to its patched version.
Serious CVE-2026-9277 shell-quote: shell-quote: Arbitrary code execution via command injection due to unescaped line terminators

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-9277). Fix: Update that package to its patched version.
Serious CVE-2026-54466 websocket-driver is a WebSocket protocol handler with pluggable I/O. P ...

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-54466). Fix: Update that package to its patched version.
Serious CVE-2025-7783 form-data: Unsafe random function in form-data

src/dispatch/static/dispatch/package-lock.json

A package you depend on has a known security hole (CVE-2025-7783). Fix: Update that package to its patched version.
Worth fixing CVE-2025-27789 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups

docs/package-lock.json

A package you depend on has a known security hole (CVE-2025-27789). Fix: Update that package to its patched version.
Worth fixing CVE-2026-44728 Babel is a compiler for writing next generation JavaScript. From 7.12. ...

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-44728). Fix: Update that package to its patched version.
Worth fixing CVE-2025-27789 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups

docs/package-lock.json

A package you depend on has a known security hole (CVE-2025-27789). Fix: Update that package to its patched version.
Worth fixing CVE-2025-27789 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups

docs/package-lock.json

A package you depend on has a known security hole (CVE-2025-27789). Fix: Update that package to its patched version.
Worth fixing CVE-2025-69873 ajv: ReDoS via $data reference

docs/package-lock.json

A package you depend on has a known security hole (CVE-2025-69873). Fix: Update that package to its patched version.
Worth fixing CVE-2025-69873 ajv: ReDoS via $data reference

docs/package-lock.json

A package you depend on has a known security hole (CVE-2025-69873). Fix: Update that package to its patched version.
Worth fixing CVE-2025-27152 axios: Possible SSRF and Credential Leakage via Absolute URL in axios Requests

docs/package-lock.json

A package you depend on has a known security hole (CVE-2025-27152). Fix: Update that package to its patched version.
Worth fixing CVE-2026-25639 axios: Axios affected by Denial of Service via __proto__ Key in mergeConfig

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-25639). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42033 axios: Axios: HTTP Transport Hijacking via Prototype Pollution

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-42033). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42035 axios: Axios: Arbitrary HTTP header injection via prototype pollution

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-42035). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42043 axios: Axios: NO_PROXY bypass via crafted URL

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-42043). Fix: Update that package to its patched version.
Worth fixing CVE-2026-44486 axios: Axios: Information disclosure of proxy credentials via HTTP redirects

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-44486). Fix: Update that package to its patched version.
Worth fixing CVE-2026-44487 axios: Axios: Information disclosure of proxy credentials via redirect flows

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-44487). Fix: Update that package to its patched version.
Worth fixing CVE-2026-44492 axios: Axios: Proxy bypass via IPv4-mapped IPv6 address non-normalization

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-44492). Fix: Update that package to its patched version.
Worth fixing CVE-2026-44495 axios: Axios: Information disclosure due to prototype pollution vulnerability

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-44495). Fix: Update that package to its patched version.
Worth fixing CVE-2026-44496 axios: Axios: Client-side Denial of Service via unescaped regex metacharacters in XSRF cookie name

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-44496). Fix: Update that package to its patched version.
Worth fixing CVE-2023-45857 axios: exposure of confidential data stored in cookies

docs/package-lock.json

A package you depend on has a known security hole (CVE-2023-45857). Fix: Update that package to its patched version.
Worth fixing CVE-2025-62718 axios: Axios: Server-Side Request Forgery and proxy bypass due to improper hostname normalization

docs/package-lock.json

A package you depend on has a known security hole (CVE-2025-62718). Fix: Update that package to its patched version.
Worth fixing CVE-2026-40175 axios: Axios: Remote Code Execution via Prototype Pollution escalation

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-40175). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42034 axios: Axios: Denial of Service via oversized streamed uploads bypassing body limits

docs/package-lock.json

A package you depend on has a known security hole (CVE-2026-42034). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42036 axios: Axios: Denial of Service via unbounded stream consumption when 'responseType: 'stream'' is used

docs/package-lock.json

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

… 203 more not shown

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ timed out

Your dependencies cross-checked against the OSV vulnerability database.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OSV-Scanner v1.9.2 · Apache-2.0

error: timeout after 400s

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: pypi: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.