mckaywrigley/chatbot-ui dependency check
AI chat for any model.
mckaywrigley/chatbot-ui: 5 critical findings, each with a fixed version. Plus 19 warnings.
Last checked against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, npm and endoflife.date.
24 things your coding agent doesn’t know about this repo
mckaywrigley/chatbot-ui on GitHub (opens in a new tab)
5 critical19 warnings46 low priority
One task with every fix, most urgent first, the file to change and why. Paste it into Claude Code, Cursor or Codex.
- CriticalVulnerabilitypackage.json
34 known vulnerabilities in next 14.1.0
EPSS: top 1%15 rated high or critical. Most serious: CVE-2025-29927, Authorization Bypass in Next.js Middleware. Upgrading to 15.5.24 fixes all of them.
- CriticalVulnerabilitypackage.json
CVE-2024-29651 in @apidevtools/json-schema-ref-parser 11.1.0
EPSS: top 45%json-schema-ref-parser Prototype Pollution issue. Fixed in 11.2.0.
- CriticalVulnerabilitypackage.json
2 known vulnerabilities in langchain 0.0.213
EPSS: top 45%1 rated high or critical. Most serious: CVE-2025-68665, LangChain serialization injection vulnerability enables secret extraction. Upgrading to 0.3.37 fixes all of them.
- CriticalEnd of life.nvmrc
Node.js 20 is end-of-life
Support ended 2026-04-30. No more security fixes — upgrade to Node.js 24 LTS (24.22.0).
- CriticalEnd of lifepackage.json
Next.js 14 is end-of-life
Support ended 2025-10-26. No more security fixes — upgrade to Next.js 16 LTS (16.4.2).
- WarningVulnerabilitypackage.json
CVE-2025-11849 in mammoth 1.6.0
EPSS: top 38%Mammoth is vulnerable to Directory Traversal. Fixed in 1.11.0.
- WarningVulnerabilitypackage-lock.json
CVE-2025-68665 in @langchain/core 0.1.17
EPSS: top 45%IndirectLangChain serialization injection vulnerability enables secret extraction. Fixed in 0.3.80.
- WarningVulnerabilitypackage.json
4 known vulnerabilities in postcss 8.4.33
EPSS: top 53%Dev onlyMost serious: CVE-2026-45623, PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments. Upgrading to 8.5.23 fixes all of them.
- WarningVulnerabilitypackage-lock.json
CVE-2025-27789 in @babel/helpers 7.23.8
EPSS: top 55%IndirectBabel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups. Fixed in 7.26.10.
- WarningVulnerabilitypackage-lock.json
CVE-2025-27789 in @babel/runtime 7.23.8
EPSS: top 55%IndirectBabel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups. Fixed in 7.26.10.
- WarningVulnerabilitypackage-lock.json
3 known vulnerabilities in @langchain/community 0.0.19
EPSS: top 69%IndirectMost serious: CVE-2026-26019, @langchain/community affected by SSRF Bypass in RecursiveUrlLoader via insufficient URL origin validation. Upgrading to 1.1.18 fixes all of them.
- WarningVulnerabilitypackage.json
CVE-2026-41907 in uuid 9.0.1
EPSS: top 70%uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided. Fixed in 11.1.1.
- WarningVulnerabilitypackage-lock.json
CVE-2026-44288 in @protobufjs/utf8 1.1.0
EPSS: top 77%Indirectprotobufjs has overlong UTF-8 decoding. Fixed in 1.1.1.
- WarningVulnerabilitypackage-lock.json
CVE-2026-44728 in @babel/plugin-transform-modules-systemjs 7.23.9
EPSS: top 93%Indirect@babel/plugin-transform-modules-systemjs generates arbitrary code when compiling malicious input. Fixed in 7.29.4.
- WarningVulnerabilitypackage-lock.json
GHSA-g2v6-rqmx-r4w6 in @vue/server-renderer 3.4.15
Indirect@vue/server-renderer: XSS via missing CR in attribute-name blacklist. Fixed in 3.5.42.
- WarningMaintenancepackage.json
@vercel/edge-config is deprecated on npm
The maintainers' deprecation notice: "This package has been renamed to @vercel/global-config. Install @vercel/global-config instead."
- WarningOutdatedpackage.json
@azure/openai 1.0.0-beta.10 is 1 major version behind
Latest release is 2.0.0. The maintainers deprecated 1.0.0-beta.10: "The Azure OpenAI client library for JavaScript beta has been retired. Please migrate to the stable OpenAI SDK for JavaScript using the migration guide: https://github.com/Azure/azure-sdk-for-js/blob/…"
- WarningOutdatedpackage.json
@hookform/resolvers 3.3.4 is 2 major versions behind
Latest release is 5.9.2.
- WarningOutdatedpackage.json
@mistralai/mistralai 0.0.8 is 2 major versions behind
Latest release is 2.7.0.
- WarningOutdatedpackage.json
date-fns 2.30.0 is 2 major versions behind
Latest release is 4.4.0.
- WarningOutdatedpackage.json
gpt-tokenizer 2.1.2 is 2 major versions behind
Latest release is 4.0.3.
- WarningOutdatedpackage.json
i18next 23.7.16 is 3 major versions behind
Latest release is 26.4.7.
- WarningOutdatedpackage.json
openai 4.24.7 is 3 major versions behind
Latest release is 7.36.0.
- WarningOutdatedpackage.json
react-day-picker 8.10.0 is 2 major versions behind
Latest release is 10.0.2.
Checked 400 packages from package.json, package-lock.json and .nvmrc against:
Add this badge to your README
It shows today’s result and links to this report, so anyone opening the repo sees what needs fixing.
[](https://stackprism.ai/check/github/mckaywrigley/chatbot-ui)What next
Want your agent to check before it adds a package? Connect Claude Code, Cursor or Codex to StackPrism. Setup steps
Ask Prism Agent about mckaywrigley/chatbot-ui
Map the repo (free) and ask what to fix first, whether an upgrade is safe, or what breaks if a service goes down. Prism Agent checks live sources before it answers.
How this report works
StackPrism read package.json, package-lock.json and .nvmrc from the default branch of mckaywrigley/chatbot-ui and checked its 400 packages against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, npm and endoflife.date. Nothing was installed or run, and there’s no AI in the findings: each one comes from a source you can open.
Vulnerabilities come from OSV.dev, with known-exploited ones from CISA marked and listed first. Runtimes, frameworks and base images are checked against endoflife.date, and packages against their registry for deprecations and major versions you’ve fallen behind. The fix task above lists every change with the file to edit.
This page refreshes every few hours; after you push a fix, “Check again” runs it now. Only the repo’s root is read. For an app in a sub-folder, paste the folder’s link into the dependency check, and for a private repo, connect GitHub.