# io.github.CloudCorpRecords/depguard (oci · ghcr.io/cloudcorprecords/depguard)

PR dependency early warning: install scripts, typosquats, downgrades, and lockfile drift.

- Trust score: 46/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/depguard`: 70/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-depguard/reneturcios-depguard.md), [page](https://verifymcp.io/servers/cloudcorprecords-depguard/reneturcios-depguard)
- oci · `ghcr.io/cloudcorprecords/depguard`: 46/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-depguard/ghcr-io-cloudcorprecords-depguard.md), [page](https://verifymcp.io/servers/cloudcorprecords-depguard/ghcr-io-cloudcorprecords-depguard)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/depguard`
- Version: `0.4.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/depguard MCP server?

io.github.CloudCorpRecords/depguard runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/depguard:0.4.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-depguard -- docker run --rm -i ghcr.io/cloudcorprecords/depguard:0.4.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-depguard": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/depguard:0.4.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-depguard": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/depguard:0.4.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-depguard -- docker run --rm -i ghcr.io/cloudcorprecords/depguard:0.4.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-depguard": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/depguard:0.4.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-depguard:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/depguard:0.4.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-depguard": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/depguard:0.4.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-depguard": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/depguard:0.4.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 41, −1)

- [functional regression] Schema quality: 143 → 161
- [functional] Package version: 0.3.0 → 0.4.0

### 2026-10-25 (score 42, +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.

### 2026-10-23 (score 41, 0)

- [functional regression] Schema quality: pass → fail
- [functional] Package version: 0.1.0 → 0.3.0
- [functional] Package version: 0.1.0 → 0.2.0

## MCP tools (3)

### `guard_path` (~197 tokens)

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).

Input parameters:

- `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, required): Local path of the repo or directory to check

### `check_package` (~140 tokens)

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.

Input parameters:

- `content` (boolean): Also run content mode against the greatest lower published version (default false)
- `name` (string, required): 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)

### `check_history` (~146 tokens)

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.

Input parameters:

- `name` (string, required): Package name, for example lodash or @scope/name
- `registry` (string): Registry to read history from (default npm)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-depguard/ghcr-io-cloudcorprecords-depguard#diagnostics

## Score history

- 2026-11-05: 46
- 2026-11-04: 46
- 2026-11-03: 45
- 2026-11-02: 45
- 2026-11-01: 44
- 2026-10-31: 44
- 2026-10-30: 43
- 2026-10-29: 43
- 2026-10-28: 42
- 2026-10-27: 42
- 2026-10-26: 41
- 2026-10-25: 42
- 2026-10-24: 41
- 2026-10-23: 41
- 2026-10-22: 41

## Common questions

### 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 container image (ghcr.io/cloudcorprecords/depguard).

### Is the io.github.CloudCorpRecords/depguard MCP server safe to use?

io.github.CloudCorpRecords/depguard scores 46 out of 100 on VerifyMCP. 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 5 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.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/depguard
- Repository: https://github.com/CloudCorpRecords/depguard
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-depguard/ghcr-io-cloudcorprecords-depguard.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-depguard/ghcr-io-cloudcorprecords-depguard.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-depguard/ghcr-io-cloudcorprecords-depguard