Enforce exact version pins across the whole MCP catalog
feat(mcp): enforce exact version pins across the whole MCP catalog
Enforce exact version pins across the whole MCP catalog9df5f8-feat-enforce-exact-version-pins-across-the-cve-2026-82021featenforce exact version pins across whole
Committed by teknium1
commit message
feat(mcp): enforce exact version pins across the whole MCP catalog
Catalog entries now follow the same supply-chain rules as pyproject
dependencies:
- n8n: install.ref main -> full commit SHA 7a9ae007 (2026-05-23,
branches/tags can be moved by the upstream owner; SHAs cannot)
- new contract test: every shipped manifest must pin exactly —
git installs need a 40-char SHA, uvx/npx-style launchers need
pkg==X / pkg@X with a digit-leading version (rejects bare names,
ranges, and npm dist-tags like @latest)
- module docstring documents the pin policy (exact version, 2-week
cooldown)
unreal-engine and linear are http transports (server runs elsewhere)
so there is nothing to pin at the transport layer.
Verified: unpinning blender-mcp in the manifest makes the contract
test fail with a named diagnostic; restoring the pin passes.Editor assessment
This commit patches CVE-2026-82021. The subject is direct and the mcp scope is right, and the body explains the supply-chain reasoning rather than restating the diff: branch and tag refs can be moved by upstream owners, while full commit SHAs cannot. It then documents the new contract test in detail, including the exact pin formats accepted for git, uvx, and npx launchers and the rejection of bare names, ranges, and dist-tags. It even records the deliberate exclusions for http transports and closes with a verification note proving the test fails when a pin is removed. Motivation, enforcement detail, and verification evidence make the change independently reviewable, which is what the top of the scale rewards.