io.github.jmshinhwa/runtime-eol-deploy-block-audit
NPM · @READYSTACK/RUNTIME-EOL-DEPLOY-BLOCK-AUDIT
Finds the end-of-life runtimes an AI assistant still writes for you — node:20, python3.9, ubuntu-22
Available components
Last scanned (3 hours ago)
Scores higher than 55% of npm servers
Category CI/CD and DevOps
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency26
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 166 tokens (~55/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
- Maintenance: pass → fail ▼ functional
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 5 Nov 2026 · Analysed npm/@readystack/runtime-eol-deploy-block-audit@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_dir ~68
Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda - sweep a folder and return every finding (licence; the full run is free for 7 days)
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | – |
| ext | string | – | optional extension filter, e.g. .html |
No output schema declared.
No examples provided.
check_file ~42
Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda - run all checks on one file by path (free)
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
check_text ~56
Runtime EOL and Deploy-Block Audit for Docker, CI and AWS Lambda - run all 54 checks on a text (free)
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | optional file name for context |
| text | string | yes | file contents |
No output schema declared.
No examples provided.
How do I install the io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server?
io.github.jmshinhwa/runtime-eol-deploy-block-audit runs locally as an npm package, launched with npx -y @readystack/runtime-eol-deploy-block-audit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @readystack/runtime-eol-deploy-block-audit
claude mcp add jmshinhwa-runtime-eol-deploy-block-audit -- npx -y @readystack/runtime-eol-deploy-block-audit
What is the io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server?
io.github.jmshinhwa/runtime-eol-deploy-block-audit is an MCP server listed in the public MCP registry as io.github.jmshinhwa/runtime-eol-deploy-block-audit. Finds the end-of-life runtimes an AI assistant still writes for you, node:20, python3.9, ubuntu-22. This page covers its npm package (@readystack/runtime-eol-deploy-block-audit).
Is the io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server safe to use?
io.github.jmshinhwa/runtime-eol-deploy-block-audit scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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.jmshinhwa/runtime-eol-deploy-block-audit MCP server expose?
io.github.jmshinhwa/runtime-eol-deploy-block-audit exposes 3 tools: check_text, check_file, check_dir. Their descriptions and schemas cost roughly 166 tokens of context every time the server is loaded.
Is the io.github.jmshinhwa/runtime-eol-deploy-block-audit MCP server still maintained?
io.github.jmshinhwa/runtime-eol-deploy-block-audit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.