nibzard/ctxt

scanned 2026-08-12 · git d9235ff

2 of 6 checks flagged a security issue

🔴 Needs attention

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

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

Leaked secrets1Vulnerable dependencies100Known OSS vulnerabilities—Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ 1 found

API keys, passwords or tokens committed into the repo.

Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

.env.example:15

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 100 found · 1 serious

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

Serious CVE-2025-55182 next: React Server Components: Pre-authentication remote code execution via unsafe deserialization

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2025-55182). Fix: Update that package to its patched version.
Worth fixing CVE-2024-21503 psf/black: ReDoS via the lines_with_leading_tabs_expanded() function in strings.py file

backend/requirements.txt

A package you depend on has a known security hole (CVE-2024-21503). Fix: Update that package to its patched version.
Worth fixing CVE-2025-58754 axios: Axios DoS via lack of data size check

frontend-next/package-lock.json

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

frontend-next/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

frontend-next/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

frontend-next/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

frontend-next/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-42264 axios: Axios: Prototype pollution allows information disclosure and request manipulation

frontend-next/package-lock.json

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

frontend-next/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

frontend-next/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-44488 axios: Axios: Denial of Service due to unenforced request and response size limits

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2026-44488). Fix: Update that package to its patched version.
Worth fixing CVE-2026-44494 axios: Axios: Man-in-the-Middle (MITM) attack via Prototype Pollution

frontend-next/package-lock.json

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

frontend-next/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

frontend-next/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-2025-62718 axios: Axios: Server-Side Request Forgery and proxy bypass due to improper hostname normalization

frontend-next/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

frontend-next/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

frontend-next/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

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2026-42036). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42037 axios: Node.js: Axios: Information disclosure via CRLF injection in multipart Content-Type header

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2026-42037). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42038 axios: Axios: Information disclosure due to `no_proxy` bypass

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2026-42038). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42039 axios: Node.js: Axios: Denial of Service via unbounded recursion in toFormData with deeply nested request data

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2026-42039). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42041 axios: Axios: Authentication bypass due to prototype pollution of HTTP error handling

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2026-42041). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42042 axios: Axios: XSRF token bypass leading to information disclosure

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2026-42042). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42044 axios: Axios: Invisible JSON Response Tampering via Prototype Pollution Gadget

frontend-next/package-lock.json

A package you depend on has a known security hole (CVE-2026-42044). Fix: Update that package to its patched version.
Worth fixing CVE-2026-44490 axios: Axios: Information disclosure and denial of service due to prototype pollution

frontend-next/package-lock.json

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

… 75 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 120s

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.