Skip to content

Dependencies

github-actions[bot] edited this page Oct 29, 2026 · 3 revisions

Dependency supply chain

No shipped dependency carries a known high or critical advisory, and a gate checks that against the registry rather than assuming it.

Source of truth the npm advisory database, via npm audit
Also reported by GitHub Dependabot (npm in / and /mcp-server, and GitHub Actions)
Governs here two dependency trees, root tooling and the MCP server, both gated
Checked by npm run verify:deps, part of npm run verify

The two trees

Each tree, with what it is for and what fails the gate.

Tree What it is Fails on
mcp-server the server's build and test tree. The published package @community-access/accessibility-agents-mcp has no runtime dependencies: the SDK, express and zod are devDependencies carried inside the bundle, and playwright, @axe-core/playwright and pdf-lib are optional peer dependencies (also devDependencies, for the tests). Its code executes on a user machine and reads their documents high, critical
root tooling only, but runs in CI on every pull request high, critical

Offline is not a pass. When the registry cannot be reached the gate exits 2 and says so, rather than printing a green line it has not earned.

Transitive dependencies with no fixed parent

Three of the MCP server's advisories were in packages it does not depend on directly: fast-uri through ajv, hono through the MCP SDK, and ip-address through express-rate-limit. Upgrading the SDK from 1.27.1 to 1.30.0 moved them forward but not far enough. The server is now on SDK 1.32.2, whose ranges are unchanged, so the overrides stay.

They are pinned in mcp-server/package.json under overrides, each to its first patched release, and each is inside the range its parent asks for.

Package Parent asks for Pinned to Advisories closed
fast-uri ^3.0.1, by ajv ^3.1.6 5
hono ^4.11.4, by the MCP SDK ^4.12.25 1
ip-address ^10.2.0, by express-rate-limit ^10.3.1 1

On 2026-10-28 the gate reported: root tooling 4 low, MCP server none. The deprecated VS Code extension, and with it a third dependency tree, was removed from the repository in this release.

An override raises a floor; it does not force an incompatible version. Remove one once its parent ships a range that cannot resolve below the patched release.

Why this gate exists

Until 7.0.1 nothing in the repository checked any dependency tree. GitHub was reporting 58 advisories on the default branch, 24 of them high, and the only place that appeared was the warning git push prints. A project that enforces accessibility on other people's code should not learn about its own supply chain from a push message.

Reproducing

npm run verify:deps
npm audit --prefix mcp-server

Sources

Clone this wiki locally