n8n-mcp-community 0.1.2 → 0.1.3

package/CHANGELOG.md

@@ -6,6 +6,55 @@ All notable changes to this project will be documented here. The format follows
 
 ## [Unreleased]
 
+## [0.1.3] - Frozen release candidate
+
+Version 0.1.3 is a frozen release candidate. Availability is established only
+by matching npm provenance, GitHub Release assets and signatures, and MCP
+Registry readbacks; this immutable entry is not rewritten after publication.
+
+### Security
+
+- MCP SDK 1.30.0 now permits the patched `@hono/node-server` 2.x line in a
+  clean standalone downstream install, so the temporary package-root override
+  is removed. The no-override consumer gate now rejects every non-zero
+  production audit and every `@hono/node-server` release below 2.0.5 or outside
+  major version 2.
+- Published 0.1.2 installations remain pinned to MCP SDK 1.29.0 and do not gain
+  this corrected downstream resolution. Its former clean-consumer closure path
+  is superseded: upgrade to 0.1.3 only after npm, GitHub, and MCP Registry
+  readbacks all verify that release.
+- The reviewed lockfile resolves `fast-uri` 3.1.5 for
+  [GHSA-7p8r-x3mc-p8w7](https://github.com/advisories/GHSA-7p8r-x3mc-p8w7)
+  (high), `hono` 4.13.0 for
+  [GHSA-8j4g-w8fx-2239](https://github.com/advisories/GHSA-8j4g-w8fx-2239)
+  (moderate), and `ip-address` 10.4.0 for
+  [GHSA-mwp4-54f8-5fhr](https://github.com/advisories/GHSA-mwp4-54f8-5fhr)
+  (high),
+  [GHSA-4xrf-jv44-h6hh](https://github.com/advisories/GHSA-4xrf-jv44-h6hh)
+  (moderate), and
+  [GHSA-22jq-vg5j-6vgg](https://github.com/advisories/GHSA-22jq-vg5j-6vgg)
+  (moderate). Development-only `brace-expansion` 5.0.9 closes
+  [GHSA-mh99-v99m-4gvg](https://github.com/advisories/GHSA-mh99-v99m-4gvg)
+  and
+  [GHSA-rgw5-rvv9-x895](https://github.com/advisories/GHSA-rgw5-rvv9-x895),
+  both high severity.
+- The published 0.1.2 MCPB vendors the earlier advisory-flagged lockfile and
+  should be upgraded only after the 0.1.3 external readbacks agree. The npm
+  tarball does not bundle transitives, so a fresh 0.1.2 npm install currently
+  re-resolves the three runtime packages to patched releases; development-only
+  `brace-expansion` is absent from that consumer graph. Its separate MCP SDK
+  1.29.0 / `@hono/node-server` residual remains until the upgrade.
+
+### Changed
+
+- Downstream dependency verification now fails closed on any advisory instead
+  of retaining the former exact 1.x backport exception.
+- The public synthetic demo now renders 0.1.3 in every version-bearing frame;
+  a version history anchored to the previous annotated release tag must extend
+  without deletion or rewriting and use a unique GIF digest per release. It
+  joins the frame-review, timing, dimension, transcript, and digest checks to
+  reject a version-only bump that silently leaves the animation stale.
+
 ## [0.1.2] - Frozen release candidate
 
 Version 0.1.2 is a frozen release candidate. Availability is established only
@@ -166,6 +215,7 @@ Registry readbacks; this immutable entry is not rewritten after publication.
   publishable history; authenticated public release receipts remain supported.
 
 [Unreleased]: #unreleased
+[0.1.3]: #013---frozen-release-candidate
 [0.1.2]: #012---frozen-release-candidate
 [0.1.1]: https://github.com/drzamarian/n8n-mcp-community/releases/tag/v0.1.1
 [0.1.0]: https://github.com/drzamarian/n8n-mcp-community/releases/tag/v0.1.0

package/README.md

@@ -47,15 +47,14 @@ diagnostics using only synthetic identifiers and documented output shapes.
 The current source candidate has been verified with:
 
 - exactly **44 tools**, **5 resources**, and **4 prompts** over real stdio;
-- **291 passing tests** and the complete verification gate on Node.js 22.23.1
+- **292 passing tests** and the complete verification gate on Node.js 22.23.1
   and 24.18.0;
 - zero findings from Gitleaks, Semgrep, Trivy, and both project-root
   production/full `npm audit` runs; all three source scanners are reproduced in
   CI, with immutable scanner/action identities;
-- a separate no-override consumer install that resolves the reviewed
-  `@hono/node-server@1.19.15` backport, accepts only an exact
-  GHSA-frvp-7c67-39w9 advisory or a fully clean advisory readback while registry
-  metadata converges, and proves the stdio runtime and exact 44/5/4 inventory;
+- a separate no-override consumer install that resolves the patched
+  `@hono/node-server` 2.x line, requires a zero-finding production audit, and
+  proves the stdio runtime and exact 44/5/4 inventory;
 - a reproducible dependency-license gate covering 224 installed package paths;
 - bounded same-origin HTTP contracts and zero-request policy-denial tests;
 - all 44 compiled tool lifecycles on disposable n8n Community 2.30.5 and 2.30.7
@@ -305,7 +304,7 @@ API. The project does not redistribute the `n8n-nodes-base` catalog and does not
 use browser cookies, interactive session routes, or runtime package downloads to
 construct one.
 
-The v0.1.2 candidate surface intentionally excludes arbitrary workflow execution,
+The v0.1.3 candidate surface intentionally excludes arbitrary workflow execution,
 credential/workflow transfer, folders, data tables, beta evaluation endpoints,
 and execution annotations. See the [roadmap](ROADMAP.md) for the annotation
 proposal retained outside the release target.

package/THIRD_PARTY_NOTICES.md

@@ -11,13 +11,13 @@ LICENSE or NOTICE file. They are exact-pinned in the lockfile, are not present
 in the runtime package or MCPB, and are accepted only at the listed version,
 license, repository, and integrity hash:
 
-| Package                 | License      | Upstream repository                                                                             |
+| Package                 | License      | Source or immutable package record                                                              |
 | ----------------------- | ------------ | ----------------------------------------------------------------------------------------------- |
 | `@humanfs/types@0.15.0` | Apache-2.0   | [humanwhocodes/humanfs](https://github.com/humanwhocodes/humanfs)                               |
 | `esrecurse@4.3.0`       | BSD-2-Clause | [estools/esrecurse](https://github.com/estools/esrecurse)                                       |
 | `flora-colossus@2.0.0`  | MIT          | [MarshallOfSound/flora-colossus](https://github.com/MarshallOfSound/flora-colossus/tree/v2.0.0) |
 | `imurmurhash@0.1.4`     | MIT          | [jensyt/imurmurhash-js](https://github.com/jensyt/imurmurhash-js)                               |
-| `keyv@4.5.4`            | MIT          | [jaredwray/keyv](https://github.com/jaredwray/keyv)                                             |
+| `keyv@4.5.4`            | MIT          | [npm registry record](https://registry.npmjs.org/keyv/4.5.4)                                    |
 | `natural-compare@1.4.0` | MIT          | [litejs/natural-compare-lite](https://github.com/litejs/natural-compare-lite)                   |
 
 Their exact SHA-512 integrity values are enforced in
@@ -26,9 +26,10 @@ or notice-file change fails the gate and requires a new review. A package with a
 missing notice file can never use this exception when it is a runtime dependency
 or bundled into a release artifact.
 
-Complete license texts are available from the linked upstream repositories and
-the SPDX identifiers above. The final MCPB must independently preserve the
-license and notice files for every dependency it actually bundles.
+Complete license texts are identified by the SPDX expressions above. The linked
+source repositories or immutable package records preserve provenance for the
+reviewed versions. The final MCPB must independently preserve the license and
+notice files for every dependency it actually bundles.
 
 `minimatch@10.2.5` is another development-only ESLint dependency and is licensed
 under the permissive Blue Oak Model License 1.0.0. Its installed package includes

package/dist/version.js

@@ -1 +1 @@
-export const PACKAGE_VERSION = "0.1.2";
+export const PACKAGE_VERSION = "0.1.3";

package/docs/compatibility.md

@@ -17,11 +17,11 @@ release evidence from the client-matrix gates that remain open.
 
 The package declares Node.js `>=22.0.0`. That engine range is an acceptance
 floor, not evidence that every later major has completed the release matrix.
-The supported release lines for v0.1.2 are Node.js 22 and 24.
+The supported release lines for v0.1.3 are Node.js 22 and 24.
 
 ## n8n Community Edition
 
-The v0.1.2 floor candidate is n8n Community Edition 2.30.5, with 2.30.7 as the
+The v0.1.3 floor candidate is n8n Community Edition 2.30.5, with 2.30.7 as the
 current comparison target. The compiled public 44-tool candidate passed fresh,
 disposable lifecycles on both versions with synthetic fixtures, API-key
 revocation, resource cleanup, enforced candidate-process egress isolation, and
@@ -33,7 +33,7 @@ browser cookies, interactive `/rest` routes, paid project transfers, arbitrary
 workflow execution, or runtime node-catalog downloads.
 
 `n8n_credentials_list` is supported only from n8n 2.30.5 onward. Project
-selectors are intentionally absent because v0.1.2 does not present paid project
+selectors are intentionally absent because v0.1.3 does not present paid project
 capabilities as Community features. Other tools may also depend on endpoint
 availability and the permissions assigned to the API key; an HTTP 403 does not
 by itself mean the endpoint is absent.
@@ -72,7 +72,7 @@ surface.
 
 ## Deliberate exclusions
 
-v0.1.2 does not include:
+v0.1.3 does not include:
 
 - folders or data tables;
 - beta evaluation endpoints;
@@ -106,9 +106,9 @@ The release gate requires, for each n8n target version:
 The local npm and unsigned MCPB candidates already pass reviewed artifact
 installation under the committed dependency policy, inventory parity,
 license/notice, SBOM generation, and checksum/reproducibility checks. The
-separate no-override consumer probe retains the upstream residual documented in
-the security model. Signature verification plus client-specific install,
-upgrade, rollback, and uninstall evidence on every claimed operating system
-remain release gates.
+separate no-override consumer probe requires the patched
+`@hono/node-server` 2.x line and a zero-finding production audit. Signature
+verification plus client-specific install, upgrade, rollback, and uninstall
+evidence on every claimed operating system remain release gates.
 
 [Back to the documentation map](README.md)

package/docs/demo-transcript.md

@@ -6,8 +6,8 @@ standards-based MCP client interaction into a short terminal-style sequence; it
 does not claim that the client narration is a project CLI command.
 
 ```text
-$ npx --yes n8n-mcp-community@0.1.2 --version
-0.1.2
+$ npx --yes n8n-mcp-community@0.1.3 --version
+0.1.3
 
 MCP client initialized n8n-community
 44 tools | 5 resources | 4 prompts
@@ -20,7 +20,7 @@ schema 1.0.0 | engine 2.0.0 | status: complete
 findings: 0 critical | 0 high | 0 medium | 0 low | 0 info
 ```
 
-The version command depicts the v0.1.2 source candidate and becomes an
+The version command depicts the v0.1.3 source candidate and becomes an
 installation route only after external npm, GitHub, and Registry readback agree.
 The initialization and tool call lines represent MCP protocol
 events, not shell commands. The Introspect output is the documented empty

package/docs/security-model.md

@@ -1,6 +1,6 @@
 # Security model
 
-This document describes the controls and residual risks of the v0.1.2 source
+This document describes the controls and residual risks of the v0.1.3 source
 candidate. It is a threat model, not a claim that the software or the connected
 n8n instance is invulnerable.
 
@@ -153,18 +153,23 @@ invitations may have irreversible or externally visible effects.
 
 ### Downstream dependency resolution
 
-The repository and bundled MCPB use a root override to resolve the patched
-`@hono/node-server` 2.x line. npm does not inherit overrides from dependency
-packages, so a fresh consumer of the npm tarball currently resolves
-`@hono/node-server@1.19.15` through MCP SDK 1.29.0. That release contains the
-reviewed backport for encoded backslashes, while advisory registries may still
-report GHSA-frvp-7c67-39w9 during metadata convergence. The affected
-`serve-static` HTTP adapter is not imported by this stdio-only server. The
-verification gate installs the candidate in a disposable consumer without
-overrides, accepts only the exact known advisory or a fully clean advisory
-readback, pins the reviewed backport version, and proves the MCP inventory still
-starts. Closure still requires a new reviewed release and a clean no-override
-consumer audit of that released version.
+MCP SDK 1.30.0 permits the patched `@hono/node-server` 2.x line directly, so
+this project no longer needs a package-root override that downstream consumers
+would not inherit. The verification gate packs the candidate, installs it in a
+disposable consumer without overrides, rejects `@hono/node-server` versions
+below 2.0.5 or outside major version 2, requires a zero-finding production
+audit, and proves the exact MCP inventory still starts. Candidate evidence does
+not establish publication: the released version must pass the same clean
+consumer audit after npm provenance and the other external release readbacks
+agree.
+
+The SDK dependency range also permits the legacy 1.x line. A separate host
+project that co-installs another dependency constraining `@hono/node-server` to
+1.x may therefore resolve a different graph from the clean standalone probe.
+This server is distributed as a standalone stdio process, not as an embeddable
+library. Projects that intentionally embed it must audit their complete
+production graph and ensure `@hono/node-server` resolves to a patched 2.x
+release.
 
 ## Threats outside this boundary
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "n8n-mcp-community",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "A security-focused MCP server for self-hosted n8n Community Edition.",
   "private": false,
   "releaseState": "candidate",
@@ -64,8 +64,7 @@
     "node": ">=22.0.0"
   },
   "overrides": {
-    "tmp": "0.2.7",
-    "@hono/node-server": "^2.0.11"
+    "tmp": "0.2.7"
   },
   "allowScripts": {},
   "scripts": {
@@ -114,7 +113,7 @@
     "verify:contributor": "npm run check:contributor && npm run test:coverage && npm run check:distribution:contributor && npm run check:consumer && npm run check:registry"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "1.29.0",
+    "@modelcontextprotocol/sdk": "1.30.0",
     "zod": "3.25.76"
   },
   "devDependencies": {

package/server.json

@@ -8,13 +8,13 @@
     "url": "https://github.com/drzamarian/n8n-mcp-community",
     "source": "github"
   },
-  "version": "0.1.2",
+  "version": "0.1.3",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "n8n-mcp-community",
-      "version": "0.1.2",
+      "version": "0.1.3",
       "transport": {
         "type": "stdio"
       },