ProvenPin this week: stricter checks and more honest version answers

ProvenPin, a library of tested code recipes for AI coding models served over a free MCP server, shipped stricter validation and more accurate version-compatibility answers during the week of Oct 23 to 29. The project added a strict tsc type-check in CI for every TypeScript recipe a pull request adds or changes, with older recipes carrying type errors placed on a known list for cleanup, and it corrected how semver ranges like ^5.3.0 and <6 are judged against tested versions. Python receipts now record every package actually installed with exact versions, not just pinned ones, making sub-dependency drift visible; the health endpoint reports 556 recipes, up from 555.

ProvenPin is a library of tested code recipes for AI coding models. Each recipe pins exact package versions, runs its own tests in a clean environment, and carries a receipt showing when it last passed. The goal is to help free and cheap models write code that actually runs. It is served over a free MCP server, no API key, no signup. This was a quality week rather than a growth week. The live health endpoint https://mcp.provenpin.com/health shows 556 recipes, up from 555 last Thursday. Most of the work went into making the checks and answers more trustworthy. Here is what shipped Oct 23 to 29 . A recipe can run and pass its tests and still have type errors your editor will flag. CI now runs a strict tsc type-check on every TypeScript recipe a pull request adds or changes. New recipes must pass. Older recipes with type errors sit on a known list that is being cleaned up in small batches PR 18 https://github.com/provenpin/provenpin/pull/18 . When you ask whether a recipe fits your project, ProvenPin compares your versions to the ones the recipe was tested on. Two fixes this week: ^5.3.0 in package.json is a range, not what you installed. It used to count as an exact match for a recipe tested on 5.3.0. Now it reads as "compatible", with a tip to pass your lockfile for an exact answer. <6 used to read as a mismatch and <5.0.0 as compatible. Now an upper bound is judged by whether it allows the tested version A recipe might pin 3 packages while the test run installs 8 once sub-dependencies come in. Python receipts now record every package that was actually installed, with exact versions, not just the pinned ones. That makes sub-dependency drift visible. All Python recipes have it PR 40 https://github.com/provenpin/provenpin/pull/40 . Claude Code: claude mcp add --transport http provenpin https://mcp.provenpin.com/mcp Cursor users can use the one click "Add to Cursor" button on the homepage https://provenpin.com . Other clients: endpoint https://mcp.provenpin.com/mcp , setup steps in the README https://github.com/provenpin/provenpin install . Site: provenpin.com https://provenpin.com . Source and receipts: github.com/provenpin/provenpin https://github.com/provenpin/provenpin .