io.github.RudrenduPaul/workspaceguard
PYPI · WORKSPACEGUARD-CLI · SCANNED AUG 22
Wraps the WorkspaceGuard CLI as a single generic MCP tool for workspace usage checks.
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 →
Supply Chain Security75
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency35
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the io.github.RudrenduPaul/workspaceguard MCP server?
io.github.RudrenduPaul/workspaceguard runs locally as a PyPI package, launched with uvx workspaceguard-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · workspaceguard-cli
claude mcp add rudrendupaul-workspaceguard -- uvx workspaceguard-cli
{
"mcpServers": {
"rudrendupaul-workspaceguard": {
"command": "uvx",
"args": [
"workspaceguard-cli"
]
}
}
} {
"servers": {
"rudrendupaul-workspaceguard": {
"command": "uvx",
"args": [
"workspaceguard-cli"
]
}
}
} codex mcp add rudrendupaul-workspaceguard -- uvx workspaceguard-cli
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rudrendupaul-workspaceguard": {
"type": "local",
"command": [
"uvx",
"workspaceguard-cli"
],
"enabled": true
}
}
} openclaw mcp add rudrendupaul-workspaceguard --command uvx --arg workspaceguard-cli
mcp_servers:
rudrendupaul-workspaceguard:
command: "uvx"
args: ["workspaceguard-cli"] {
"McpServers": {
"rudrendupaul-workspaceguard": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"workspaceguard-cli"
]
}
}
} assistant mcp add rudrendupaul-workspaceguard -t stdio -c uvx -a workspaceguard-cli
{
"mcpServers": {
"rudrendupaul-workspaceguard": {
"command": "uvx",
"args": [
"workspaceguard-cli"
]
}
}
} 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.
- 13 Aug 26 0
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → pass ▲ functional
- 12 Aug 26 0
- Security disclosure: pass → unverified ▼ functional
- 11 Aug 26 0
First indexed and scored.
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 22 Aug 2026 · Analysed pypi/workspaceguard-cli@0.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Vulnerabilities 13 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-537c-gmf6-5ccf | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-g6cj-pr64-35w5 | CVE-2026-69247 | high | yes | |
| GHSA-jwv3-5hgf-82ww | CVE-2026-69249 | high | yes | |
| GHSA-m2h6-j472-rp4c | CVE-2026-69248 | medium | yes | |
| GHSA-m959-cc7f-wv43 | CVE-2026-34073 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-p423-j2cm-9vmq | CVE-2026-39892 | medium | yes | |
| GHSA-r6ph-v2qm-q3c2 | CVE-2026-26007 | high | yes | |
| PYSEC-2026-2141 | CVE-2026-26007 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N | yes |
| PYSEC-2026-35 | CVE-2026-34073 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-3552 | CVE-2026-69247 | none | yes | |
| PYSEC-2026-3553 | CVE-2026-69249 | none | yes | |
| PYSEC-2026-3554 | CVE-2026-69248 | none | yes | |
| PYSEC-2026-36 | CVE-2026-39892 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| Tree resolution | Complete |
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.
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.