Skip to content

docs(security): record why the open advisories are unreachable here - #58

Open
CDVolvik wants to merge 1 commit into
masterfrom
docs/dependency-reachability
Open

docs(security): record why the open advisories are unreachable here#58
CDVolvik wants to merge 1 commit into
masterfrom
docs/dependency-reachability

Conversation

@CDVolvik

Copy link
Copy Markdown
Owner

What & why

GitHub reports seven open advisories on the default branch, one of them high. Anyone landing on this repo sees that badge before they read a line of code, and for an EHR-adjacent tool that is the wrong first impression to leave unexplained.

All seven are transitive through @modelcontextprotocol/sdk:

sdk -> @hono/node-server -> hono           (4 advisories)
sdk -> express-rate-limit -> ip-address    (3, including the high SSRF one)

These are production-tree dependencies, not dev-only — writing them off as dev noise would be wrong. What makes them unreachable is the transport. src/index.ts only ever constructs StdioServerTransport; it never instantiates an HTTP or SSE transport, so none of that code is loaded, and none of it is bundled. Confirmed against a fresh build: dist/index.js has zero matches for hono, express-rate-limit, or ip-address.

This adds a Dependency advisories section to SECURITY.md recording that reasoning, plus a two-line command so a reader can verify it instead of taking it on faith.

It also says plainly that reachability is a reason not to panic, not a reason to skip the bump — so this does not calcify into a standing excuse to stop patching.

Note on overlap

Does not touch the stale-account line in SECURITY.md; #56 already fixes that. This section is additive and sits lower in the file.

Checklist

  • format:check, lint, typecheck, test, build all pass locally
  • Tests added/updated — n/a, documentation-only change
  • Tools remain read-only; no secrets committed
  • No CHANGELOG entry: no behaviour, dependency, or tool-surface change

Seven Dependabot alerts are open against the default branch, one of them
high. All seven are transitive through @modelcontextprotocol/sdk:

  sdk -> @hono/node-server -> hono            (4)
  sdk -> express-rate-limit -> ip-address     (3, incl. the high SSRF one)

They are production-tree dependencies, not dev-only, so dismissing them as
dev noise would be wrong. What makes them unreachable is the transport:
src/index.ts only ever constructs StdioServerTransport, never an HTTP or
SSE one, so none of that code is loaded or bundled. Verified against a
fresh build - dist/index.js has zero matches for any of the three.

Adds a Dependency advisories section to SECURITY.md with the reasoning and
a two-line command so a reader can confirm it rather than take it on faith.

States explicitly that reachability is a reason not to panic, not a reason
to skip the bump, so this does not become a standing excuse to stop
patching.

Docs only. No dependency, behaviour, or tool-surface change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant