n8n-mcp-community 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -6,6 +6,30 @@ All notable changes to this project will be documented here. The format follows
 
 ## [Unreleased]
 
+## [0.3.1] - Frozen release candidate
+
+Version 0.3.1 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
+
+- The reviewed runtime lock graph now resolves patched `fast-uri`, `hono`,
+  `ip-address`, and `qs` releases, clearing the complete npm production audit
+  instead of applying the incomplete package-by-package Dependabot proposals.
+- CodeQL initialization and analysis now use the same immutable v4.38.2 commit,
+  avoiding mixed-version workflow failures.
+- The release toolchain no longer loads the vulnerable, unfixed `node-forge`
+  dependency pulled by the upstream MCPB CLI. It validates the pinned official
+  v0.4 schema, creates and extracts bounded canonical ZIPs locally, and keeps
+  CMS signing and verification on OpenSSL.
+
+### Changed
+
+- Current compatible development releases of `@types/node`, ESLint, `globals`,
+  Prettier, `typescript-eslint`, and `yaml` keep the verification toolchain
+  current without changing the public 44-tool MCP contract.
+
 ## [0.3.0] - Frozen release candidate
 
 Version 0.3.0 is a frozen release candidate. Availability is established only
@@ -343,6 +367,7 @@ Registry readbacks; this immutable entry is not rewritten after publication.
   publishable history; authenticated public release receipts remain supported.
 
 [Unreleased]: #unreleased
+[0.3.1]: #031---frozen-release-candidate
 [0.3.0]: #030---frozen-release-candidate
 [0.2.1]: #021---frozen-release-candidate
 [0.2.0]: #020---frozen-release-candidate

package/README.md

@@ -104,7 +104,7 @@ how to check the download.
 The current source candidate has been verified with:
 
 - exactly **44 tools**, **5 resources**, and **4 prompts** over real stdio;
-- **313 passing tests** locally on Node.js 24.19.0; CI and release gates require
+- **319 passing tests** locally on Node.js 24.21.0; CI and release gates require
   the pinned Node.js 22.23.1 and 24.18.0 matrix;
 - zero findings from Gitleaks, Semgrep, Trivy, and both project-root
   production/full `npm audit` runs; all three source scanners are reproduced in
@@ -112,7 +112,7 @@ The current source candidate has been verified with:
 - 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;
+- a reproducible dependency-license gate covering 186 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
   instances with egress isolation, revoked keys, cleanup, and zero residue; and
@@ -291,7 +291,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.3.0 candidate surface intentionally excludes arbitrary workflow execution,
+The v0.3.x 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/ROADMAP.md

@@ -18,7 +18,7 @@ maintainer approval.
 
 ## Accepted backlog proposal
 
-Execution annotations remain a coherent two-tool proposal outside v0.3.0:
+Execution annotations remain a coherent two-tool proposal outside v0.3.x:
 
 - `n8n_executions_get_tags`
 - `n8n_executions_update_tags`

package/THIRD_PARTY_NOTICES.md

@@ -5,20 +5,18 @@ licenses; `package-lock.json` is the exact dependency record and
 `npm run licenses:check` validates every installed package path.
 
 The npm runtime tarball does not bundle dependencies. The following packages
-are development-only transitive dependencies of ESLint or the MCPB build CLI.
+are development-only transitive dependencies of ESLint.
 Their published npm tarballs declare an SPDX license but omit a top-level
 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      | 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          | [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)                   |
+| 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)                     |
+| `imurmurhash@0.1.4`     | MIT          | [jensyt/imurmurhash-js](https://github.com/jensyt/imurmurhash-js)             |
+| `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
 `scripts/verify-dependency-licenses.mjs`. Any version, license, integrity, role,
@@ -37,13 +35,14 @@ the license file; the official license text and required notice link are
 <https://blueoakcouncil.org/license/1.0.0>. It is not bundled in the npm runtime
 tarball.
 
-Two development-only MCPB build dependencies offer alternative licenses. This
-project selects the permissive alternative shown below. The gate pins the exact
-version, declared expression, selected license, repository, and integrity hash;
-both installed packages include the selected license text and neither is bundled
-in the npm runtime tarball or MCPB.
-
-| Package            | Declared expression       | Selected license |
-| ------------------ | ------------------------- | ---------------- |
-| `node-forge@1.4.0` | `BSD-3-Clause OR GPL-2.0` | BSD-3-Clause     |
-| `type-fest@0.21.3` | `MIT OR CC0-1.0`          | MIT              |
+The pinned `mcpb/mcpb-manifest-v0.4.schema.json` file comes from the official
+`@anthropic-ai/mcpb@2.1.2` source at immutable tag `v2.1.2` in
+[modelcontextprotocol/mcpb](https://github.com/modelcontextprotocol/mcpb/tree/v2.1.2).
+Copyright 2025 Anthropic, PBC. It is used under the MIT License reproduced in
+`mcpb/OFFICIAL_SCHEMA_LICENSE`. The immutable upstream schema has SHA-256
+`068557824c651d6d49b86ad132adeafe62ca788d918b3e1e2b224bf0f91320fd`.
+The checked-in JSON is semantically identical but formatted with the repository's
+Prettier policy; its SHA-256 is
+`dae6c4a11da73fcce9adda27dface6049a90b31765623e0a445e485b321e4d46`.
+The schema is a development-time validator and is not included in the npm
+runtime tarball or the MCPB artifact.

package/dist/version.js

@@ -1 +1 @@
-export const PACKAGE_VERSION = "0.3.0";
+export const PACKAGE_VERSION = "0.3.1";

package/docs/compatibility.md

@@ -9,7 +9,7 @@ release evidence from the client-matrix gates that remain open.
 | ---------------------- | ------------------------------------------------------------- |
 | Node.js 22.23.1        | Pinned CI/release target; exact candidate proof comes from CI |
 | Node.js 24.18.0        | Pinned CI/release target; exact candidate proof comes from CI |
-| Node.js 24.19.0        | Current complete local candidate gate                         |
+| Node.js 24.21.0        | Current complete local candidate gate                         |
 | MCP transport          | stdio inventory verified as 44 tools, 5 resources, 4 prompts  |
 | macOS on Apple silicon | Development and local verification environment                |
 | Linux and Windows      | No public release claim yet                                   |
@@ -18,7 +18,7 @@ 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.3.0 are Node.js 22 and 24.
+The supported release lines for v0.3.x are Node.js 22 and 24.
 
 ## Upgrading to 0.3.0
 
@@ -48,7 +48,7 @@ names. MCP clients receive these constraints when they reconnect.
 The connection values are unchanged. Global npm users keep the same client
 entry. Users who followed the 0.1.x npx guide must replace the pinned
 `n8n-mcp-community@0.1.4` argument with `n8n-mcp-community@latest` or
-`n8n-mcp-community@0.3.0`. After updating, restart the MCP client and confirm the
+`n8n-mcp-community@0.3.1`. After updating, restart the MCP client and confirm the
 version and 44/5/4 inventory.
 
 Since 0.2.0, the 14 unsafe tools no longer publish or require a `confirmation` field;
@@ -59,7 +59,7 @@ update and rollback steps.
 
 ## n8n Community Edition
 
-The v0.3.0 floor candidate is n8n Community Edition 2.30.5, with 2.30.7 as the
+The v0.3.x 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
@@ -71,7 +71,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.3.0 does not present paid project
+selectors are intentionally absent because v0.3.x 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.
@@ -110,7 +110,7 @@ surface.
 
 ## Deliberate exclusions
 
-v0.3.0 does not include:
+v0.3.x does not include:
 
 - folders or data tables;
 - beta evaluation endpoints;

package/docs/installation.md

@@ -92,7 +92,7 @@ unsafe tools.
 
 Global npm users do not edit the client entry. If you followed the 0.1.x npx
 guide, your client is pinned to `n8n-mcp-community@0.1.4`: replace that argument
-with `n8n-mcp-community@latest` or `n8n-mcp-community@0.3.0`. Restart the client,
+with `n8n-mcp-community@latest` or `n8n-mcp-community@0.3.1`. Restart the client,
 run the npx version check below, and confirm the 44/5/4 inventory.
 
 If custom code sends raw tool-call JSON, remove the former `confirmation` field

package/docs/provenance.md

@@ -53,15 +53,14 @@ fails on:
 - missing license metadata;
 - a package that declares a license or notice file but omits it.
 
-The current source candidate covers 224 installed package paths representing
-222 unique components: 93 runtime paths and 131 development paths. After two
-explicit permissive-alternative selections, the effective licenses are 184 MIT,
-15 ISC, 13 Apache-2.0, 7 BSD-2-Clause, 4 BSD-3-Clause, and 1
-BlueOak-1.0.0, with no missing integrity, license, or documented notice. Six
-exact-pinned development-only packages use the reviewed missing-file exception,
-and two development-only packages use exact-pinned alternative-license
-selections described in [third-party notices](../THIRD_PARTY_NOTICES.md). These
-counts must be regenerated after any lockfile change.
+The current source candidate covers 186 installed package paths representing
+185 unique components: 93 runtime paths and 93 development paths. The effective
+licenses are 151 MIT, 11 ISC, 13 Apache-2.0, 7 BSD-2-Clause, 3 BSD-3-Clause,
+and 1 BlueOak-1.0.0, with no missing integrity, license, or documented notice.
+Four exact-pinned development-only packages use the reviewed missing-file
+exception described in [third-party notices](../THIRD_PARTY_NOTICES.md). No
+package currently needs an alternative-license selection. These counts must be
+regenerated after any lockfile change.
 
 PyYAML 6.0.3 was used as local audit tooling to parse official OpenAPI material
 and compare endpoint schemas. It is not imported by the TypeScript runtime or
@@ -83,9 +82,9 @@ Generate the release runtime CycloneDX SBOM from the committed lockfile with:
 npm run sbom > sbom.cdx.json
 ```
 
-This runtime-only SBOM contains 75 unique production components for the shared
+This runtime-only SBOM contains 78 unique production components for the shared
 npm/MCPB runtime graph. Maintainers may separately generate the complete
-222-component development graph with `npm run sbom:full`; it is audit evidence,
+185-component graph with `npm run sbom:full`; it is audit evidence,
 not the release artifact SBOM. Every release candidate must carry a runtime
 SBOM for the npm package and MCPB, plus SHA-256 checksums and signatures tied to
 the exact Git revision; availability is established only by the corresponding

package/docs/security-model.md

@@ -1,6 +1,6 @@
 # Security model
 
-This document describes the controls and residual risks of the v0.3.0 source
+This document describes the controls and residual risks of the v0.3.1 source
 candidate. It is a threat model, not a claim that the software or the connected
 n8n instance is invulnerable.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "n8n-mcp-community",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "A security-focused MCP server for self-hosted n8n Community Edition.",
   "private": false,
   "releaseState": "candidate",
@@ -62,9 +62,6 @@
   "engines": {
     "node": ">=22.0.0"
   },
-  "overrides": {
-    "tmp": "0.2.7"
-  },
   "allowScripts": {},
   "scripts": {
     "audit:full": "node scripts/run-npm-audit.mjs full",
@@ -118,17 +115,16 @@
     "zod": "3.25.76"
   },
   "devDependencies": {
-    "@anthropic-ai/mcpb": "2.1.2",
     "@eslint/js": "10.0.1",
-    "@types/node": "22.20.1",
+    "@types/node": "22.20.5",
     "ajv": "8.20.0",
     "ajv-formats": "3.0.1",
-    "eslint": "10.8.0",
+    "eslint": "10.12.0",
     "fflate": "0.8.3",
-    "globals": "17.9.0",
-    "prettier": "3.9.6",
+    "globals": "17.13.0",
+    "prettier": "3.9.9",
     "typescript": "5.9.3",
-    "typescript-eslint": "8.65.0",
-    "yaml": "2.9.0"
+    "typescript-eslint": "8.71.0",
+    "yaml": "2.9.1"
   }
 }

package/server.json

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