io.github.CloudCorpRecords/depguard
NPM · @RENETURCIOS/DEPGUARD · 2 COMPONENTS
PR dependency early warning: install scripts, typosquats, downgrades, and lockfile drift.
Available components
Last scanned (21 hours ago)
Scores higher than 38% of npm servers
Category Security
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 483 tokens (~161/item across 3 items; 3 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 Management43
- Stability observed for 13 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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 143 → 161 ▼ functional
- Package version: 0.3.0 → 0.4.0 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +10
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
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 4 Nov 2026 · Analysed npm/@reneturcios/depguard@0.4.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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_history ~146
Analyze a package's registry publish history for the staged worm pattern (a 0.0.0-stage stub, a decoy release, then a rapid regressed patch holding dist-tags.latest), plus publisher and maintainer changes, repository slug changes, and provenance drops between consecutive versions. The registry defaults to npm; with registry pypi it reads PyPI history instead (the same timeline checks, plus yanked-version findings, since PyPI publishes no per-version publisher data). Registry metadata only; no tarballs are downloaded.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name, for example lodash or @scope/name |
| registry | string | – | Registry to read history from (default npm) |
No output schema declared.
No examples provided.
check_package ~140
Grade a single package name (and optional version): typosquat distance against a bundled popular-names list and version pattern checks offline; with online true, registry checks for version age under 7 days, publisher change versus the previous version, provenance attestation, and deprecation.
| Name | Type | Req | Description |
|---|---|---|---|
| content | boolean | – | Also run content mode against the greatest lower published version (default false) |
| name | string | yes | Package name, for example lodash or @scope/name |
| online | boolean | – | Also run npm registry checks (default false) |
| version | string | – | Version to check (default: offline name checks only, or the registry latest when online) |
No output schema declared.
No examples provided.
guard_path ~197
Diff a repo's dependency manifests and lockfiles against a base (git ref or directory) and grade every added, removed, and changed dependency: install scripts, typosquat-shaped names, downgrades, prerelease jumps, widened ranges, and lockfile drift. Fully offline unless online is true, which adds npm registry checks (version age, publisher change, provenance, deprecation).
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Git ref to diff against (for example HEAD~1 or a tag) |
| base_path | string | – | Directory holding the base manifest set to diff against |
| content | boolean | – | Also run content mode: fetch both versions' tarballs and diff the install-time surface statically, nothing installed or executed (default false) |
| online | boolean | – | Also run npm registry checks (default false; the base verdict never needs the network) |
| path | string | yes | Local path of the repo or directory to check |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/depguard MCP server?
io.github.CloudCorpRecords/depguard runs locally as an npm package, launched with npx -y @reneturcios/depguard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/depguard
claude mcp add cloudcorprecords-depguard -- npx -y @reneturcios/depguard
What is the io.github.CloudCorpRecords/depguard MCP server?
io.github.CloudCorpRecords/depguard is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/depguard. PR dependency early warning: install scripts, typosquats, downgrades, and lockfile drift. This page covers its npm package (@reneturcios/depguard).
Is the io.github.CloudCorpRecords/depguard MCP server safe to use?
io.github.CloudCorpRecords/depguard scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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.CloudCorpRecords/depguard MCP server expose?
io.github.CloudCorpRecords/depguard exposes 3 tools: guard_path, check_package, check_history. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/depguard MCP server still maintained?
io.github.CloudCorpRecords/depguard is still listed as active in the MCP registry. We last reached this channel on 4 November 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.CloudCorpRecords/depguard MCP server under?
io.github.CloudCorpRecords/depguard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.