io.github.kyungseopk1m/semver-checks
NPM · SEMVER-CHECKS · SCANNED SEP 21
Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to kyungseopk1m/semver-checks). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 27 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1151 tokens (~575/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.kyungseopk1m/semver-checks MCP server?
io.github.kyungseopk1m/semver-checks runs locally as an npm package, launched with npx -y semver-checks. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · semver-checks
claude mcp add kyungseopk1m-semver-checks -- npx -y semver-checks
{
"mcpServers": {
"kyungseopk1m-semver-checks": {
"command": "npx",
"args": [
"-y",
"semver-checks"
]
}
}
} {
"servers": {
"kyungseopk1m-semver-checks": {
"command": "npx",
"args": [
"-y",
"semver-checks"
]
}
}
} codex mcp add kyungseopk1m-semver-checks -- npx -y semver-checks
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kyungseopk1m-semver-checks": {
"type": "local",
"command": [
"npx",
"-y",
"semver-checks"
],
"enabled": true
}
}
} openclaw mcp add kyungseopk1m-semver-checks --command npx --arg -y --arg semver-checks
mcp_servers:
kyungseopk1m-semver-checks:
command: "npx"
args: ["-y", "semver-checks"] {
"McpServers": {
"kyungseopk1m-semver-checks": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"semver-checks"
]
}
}
} assistant mcp add kyungseopk1m-semver-checks -t stdio -c npx -a -y semver-checks
{
"mcpServers": {
"kyungseopk1m-semver-checks": {
"command": "npx",
"args": [
"-y",
"semver-checks"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −2
- Stability: pass → 0.90 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/semver-checks@0.13.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | kyungseopk1m/semver-checks |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/kyungseopk1m/semver-checks/.github/workflows/publish.yml@refs/tags/v0.13.0 |
| Rekor log index | 2580427193 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:78df7c0ea89881fae81532e9f6ed31d2ff864df83f6bb335090d5881fa0bb71a9fbb84425b880b0e1725ae8122a4c3f6d87bf89a35e3f199697789341 |
Background: How many MCP packages publish verified provenance →
Dependencies 108 packages
| Packages resolved | 108 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
semver_compare ~752
Compare two versions of a TypeScript library and detect breaking API changes. Either side can be a filesystem path, a git ref, or an npm spec, so a working tree can be compared against the published release without checking anything out. Returns the recommended SemVer bump (major/minor/patch) and a list of changes. Each change carries a confidence: "proven" (a structurally confident break — gate on these) or "heuristic" (a conservative major the tool could not prove safe — surface for review). summary.majorProven / majorReview split the major count accordingly. Pass "declared" to have the tool grade the bump the release writes down instead of just recommending one. The "gate" field answers what each CLI gate would do with this report, which is what its exit code carries: "strict" fails only on a proven break and is the one safe to leave on every build, while "strictReview" also fails on a major the analyzer could not prove. They are not two strengths of the same check. A passing "strict" is not a clean bill of health, because a real break it could not prove stays review-only; "green means safe" is a claim only "strictReview" can make. Report both rather than reading "strict": "pass" as "nothing broke". Passing "declared" changes the question both gates answer: the release is then graded against the bump it writes down, so a major it already declares passes both.
| Name | Type | Req | Description |
|---|---|---|---|
| declared | string | – | The bump this release declares, or "auto" to read it from .changeset/*.md and then the two package.json versions. Adds a "declaration" verdict to the report: "mismatch" when a proven break outranks t… |
| entry | – | – | Entry file relative to project root (e.g. "src/index.ts"). Pass an array or a comma-separated string for a package with several entry points. Auto-detected from package.json if omitted. |
| installDeps | boolean | – | Install dependencies before analysis (needed for local paths without node_modules) |
| maxChanges | integer | – | How many changes to include (default 50). They are ordered proven breaks first, then additions, then review-only ones, so the cap drops the least actionable end. "summary" always counts every change,… |
| new | string | – | New version: a filesystem path, a git ref, or an npm spec. Defaults to current directory. |
| newAs | string | – | Force "new" to be treated as a filesystem path, a git ref, or an npm spec. "ref" is an accepted spelling of "git". |
| old | string | yes | Old version: a filesystem path, a git ref (tag, branch, commit SHA), or an npm spec. A "name@version" that is not an existing path is read as npm (e.g. "lodash@4.17.21", "lodash@latest"); prefix with… |
| oldAs | string | – | Force "old" to be treated as a filesystem path, a git ref, or an npm spec. "ref" is an accepted spelling of "git". Only needed when auto-detection would read the input as the wrong kind, which is wha… |
No output schema declared.
No examples provided.
semver_snapshot ~399
Extract the public API surface of a TypeScript project as a structured JSON snapshot, keyed by export subpath. Useful for inspecting what a library exports. The source can be a filesystem path, a git ref, or an npm spec, the same three forms semver_compare takes. Returns each symbol's name and kind by default; pass "detail" for full type shapes, which is far larger.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | boolean | – | Include each symbol's full type shape instead of just its kind. A shape runs a median of about 370 bytes and a wide interface tens of kilobytes, against about 35 for a name and a kind, so a large pac… |
| entry | – | – | Entry file relative to project root (e.g. "src/index.ts"). Pass an array or a comma-separated string for a package with several entry points. |
| installDeps | boolean | – | Install dependencies before analysis |
| maxBytes | integer | – | Byte budget for the symbols in the response (default 40000). Symbols are included while it lasts, and an "omitted" field then reports how many were left out along with the total. No symbol is exempt:… |
| path | string | – | Project source: a filesystem path, a git ref, or an npm spec such as "lodash@4.17.21". Defaults to current directory. |
| pathAs | string | – | Force "path" to be treated as a filesystem path, a git ref, or an npm spec. "ref" is an accepted spelling of "git". Only needed when auto-detection would read the input as the wrong kind. |
No output schema declared.
No examples provided.
What is the io.github.kyungseopk1m/semver-checks MCP server?
io.github.kyungseopk1m/semver-checks is an MCP server listed in the public MCP registry as io.github.kyungseopk1m/semver-checks. Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump. This page covers its npm package (semver-checks).
Is the io.github.kyungseopk1m/semver-checks MCP server safe to use?
io.github.kyungseopk1m/semver-checks scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.kyungseopk1m/semver-checks MCP server expose?
io.github.kyungseopk1m/semver-checks exposes 2 tools: semver_compare, semver_snapshot. Their descriptions and schemas cost roughly 1,151 tokens of context every time the server is loaded.
Is the io.github.kyungseopk1m/semver-checks MCP server still maintained?
io.github.kyungseopk1m/semver-checks is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.kyungseopk1m/semver-checks MCP server under?
io.github.kyungseopk1m/semver-checks declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.