You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5aa21e6
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: SECURITY.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,17 +49,17 @@ The failed commands token-goat learns fixes for are kept only as keyed digests,
49
49
50
50
## Dependency advisories
51
51
52
-
`npm audit` reports Token-Goat clean for anyone who installs it, and that has been true of a default install since the embedding library that carried every finding was removed. This repository's own tree carries two open findings, described below the table, both development only: body-parser and fast-uri. Apart from them it is clean, development dependencies included: `adm-zip`, `hono`, `proxy-addr` and `source-map-js` were resolved to patched versions through the lock-file refresh, not bumped by hand the day a fix was published -- see [`.github/dependabot.yml`](.github/dependabot.yml) for why a plain `npm update` isn't the fix. All three numbers below are reproducible with the commands shown. The one place an advisory can still reach is the optional native runtime, which a default install does not carry, and it is described further down rather than folded into these rows.
52
+
`npm audit` reports Token-Goat clean for anyone who installs it, and that has been true of a default install since the embedding library that carried every finding was removed. This repository's own tree carries one open finding, described below the table, development only: body-parser. Apart from it it is clean, development dependencies included: `adm-zip`, `hono`, `proxy-addr` and `source-map-js` were resolved to patched versions through the lock-file refresh, not bumped by hand the day a fix was published -- see [`.github/dependabot.yml`](.github/dependabot.yml) for why a plain `npm update` isn't the fix. All three numbers below are reproducible with the commands shown. The one place an advisory can still reach is the optional native runtime, which a default install does not carry, and it is described further down rather than folded into these rows.
53
53
54
54
| What you scan | Command | Result |
55
55
| --- | --- | --- |
56
-
| this repository |`npm audit`|2 findings, both development only: 1 high, body-parser GHSA-27r3-jxmh-p828; 1 moderate, fast-uri GHSA-w74x-v6f9-j3xg and three more; see below |
56
+
| this repository |`npm audit`|1 finding, development only: 1 high, body-parser GHSA-27r3-jxmh-p828; see below |
57
57
| an install without optional packages |`npm install --omit=optional token-goat` then `npm audit --omit=dev --omit=optional`| clean, 2 packages |
58
58
| a default install |`npm install token-goat` then `npm audit --omit=dev`| clean, 62 packages |
59
59
60
-
The first open finding is [GHSA-27r3-jxmh-p828](https://github.com/advisories/GHSA-27r3-jxmh-p828), high severity: `body-parser` 2.0.0 to 2.3.0 can be made to spend excessive resources on trailing bytes after a compressed request body, a denial of service. It is in the development tree only, through `@modelcontextprotocol/sdk` and `express`, so neither install row above carries it, and Token-Goat does not reach it: the shipped MCP server is the in-house stdio one in `src/mcp_jsonrpc.ts`, and the only listener, in `src/hook_server.ts`, is a `net.createServer` socket that never parses an HTTP body. The fixed release, 2.4.0, was published on 2026-10-22, inside the seven-day `cooldown` in [`.github/dependabot.yml`](.github/dependabot.yml), so the lock-file refresh takes it after 2026-10-29. This row goes back to clean only once both findings have cleared.
60
+
The open finding is [GHSA-27r3-jxmh-p828](https://github.com/advisories/GHSA-27r3-jxmh-p828), high severity: `body-parser` 2.0.0 to 2.3.0 can be made to spend excessive resources on trailing bytes after a compressed request body, a denial of service. It is in the development tree only, through `@modelcontextprotocol/sdk` and `express`, so neither install row above carries it, and Token-Goat does not reach it: the shipped MCP server is the in-house stdio one in `src/mcp_jsonrpc.ts`, and the only listener, in `src/hook_server.ts`, is a `net.createServer` socket that never parses an HTTP body. The fixed release, 2.4.0, was published on 2026-10-22, inside the seven-day `cooldown` in [`.github/dependabot.yml`](.github/dependabot.yml), so the lock-file refresh takes it after 2026-10-29. This row goes back to clean only once this finding has cleared.
61
61
62
-
The second open finding is fast-uri, rated moderate, with four advisories: [GHSA-w74x-v6f9-j3xg](https://github.com/advisories/GHSA-w74x-v6f9-j3xg) and [GHSA-wjr9-j795-jxcr](https://github.com/advisories/GHSA-wjr9-j795-jxcr) are moderate, and [GHSA-xhq7-xmqj-769h](https://github.com/advisories/GHSA-xhq7-xmqj-769h) and [GHSA-333x-w4r6-6crp](https://github.com/advisories/GHSA-333x-w4r6-6crp) are low. `npm audit` reports versions 3.0.0 to 3.1.8. It is development only: `npm ls fast-uri --all --package-lock-only` shows two chains, both starting at `@modelcontextprotocol/sdk` 1.32.1, a development dependency. One runs through its own `ajv` 8.20.0 and the other through `ajv-formats` 3.0.1, which carries its own `ajv` 8.20.0. Both ajv copies depend on `fast-uri` `^3.0.1`, and the root `overrides` block pins it to `^3.1.6`, so the lock resolves 3.1.8, and an install of token-goat does not get it. Token-goat's shipped code does not reach it: nothing under `src/` imports `@modelcontextprotocol/sdk`, `ajv`, `ajv-formats` or `fast-uri`, and the only mentions are two comments, in `src/mcp_jsonrpc.ts` and `src/hooks_common.ts`. The fixed 3.1.9 was published on 2026-10-19, inside the seven-day `cooldown`, so the lock-file refresh takes it after 2026-10-26, and this finding clears then.
62
+
fast-uri was the second finding, rated moderate, with four advisories: [GHSA-w74x-v6f9-j3xg](https://github.com/advisories/GHSA-w74x-v6f9-j3xg), [GHSA-wjr9-j795-jxcr](https://github.com/advisories/GHSA-wjr9-j795-jxcr), [GHSA-xhq7-xmqj-769h](https://github.com/advisories/GHSA-xhq7-xmqj-769h) and [GHSA-333x-w4r6-6crp](https://github.com/advisories/GHSA-333x-w4r6-6crp). They covered `fast-uri` 3.0.0 to 3.1.8. The lock now resolves 3.1.9, and `npm audit` no longer lists the package. The 3.1.9 release was published on 2026-10-19, and its seven-day `cooldown` ended on 2026-10-26, so this finding cleared then.
63
63
64
64
The repository carries an `overrides` block in [`package.json`](package.json) that pins nine packages to patched versions, and **npm applies `overrides` only in the root project**, so those pins do not travel to anyone who installs Token-Goat as a dependency. That distinction used to matter a great deal, because a clean repository scan was standing in for an install that was not clean. It decides one thing now, and the section on the embedding runtime below says which. Otherwise the packages those pins were protecting against are not in a consumer's tree at all, whether or not the pins travel; the block stays because the development tree still resolves them.
0 commit comments