io.github.homeofe/supply-chain-guard
NPM · SUPPLY-CHAIN-GUARD · SCANNED OCT 1
Supply-chain malware scanner and MCP server: vet packages in 15 ecosystems before install, offline.
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 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
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to homeofe/supply-chain-guard). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 623 tokens (~207/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 Management17
- Stability observed for 5 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 4 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
How do I install the io.github.homeofe/supply-chain-guard MCP server?
io.github.homeofe/supply-chain-guard runs locally as an npm package, launched with npx -y supply-chain-guard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · supply-chain-guard
claude mcp add homeofe-supply-chain-guard -- npx -y supply-chain-guard
{
"mcpServers": {
"homeofe-supply-chain-guard": {
"command": "npx",
"args": [
"-y",
"supply-chain-guard"
]
}
}
} {
"servers": {
"homeofe-supply-chain-guard": {
"command": "npx",
"args": [
"-y",
"supply-chain-guard"
]
}
}
} codex mcp add homeofe-supply-chain-guard -- npx -y supply-chain-guard
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"homeofe-supply-chain-guard": {
"type": "local",
"command": [
"npx",
"-y",
"supply-chain-guard"
],
"enabled": true
}
}
} openclaw mcp add homeofe-supply-chain-guard --command npx --arg -y --arg supply-chain-guard
mcp_servers:
homeofe-supply-chain-guard:
command: "npx"
args: ["-y", "supply-chain-guard"] {
"McpServers": {
"homeofe-supply-chain-guard": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"supply-chain-guard"
]
}
}
} assistant mcp add homeofe-supply-chain-guard -t stdio -c npx -a -y supply-chain-guard
{
"mcpServers": {
"homeofe-supply-chain-guard": {
"command": "npx",
"args": [
"-y",
"supply-chain-guard"
]
}
}
} 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.
- 1 Oct 26 +12
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 30 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 6.3.3 → 6.4.0 functional
- 29 Sept 26 0
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 6.3.2 → 6.3.3 functional
- 28 Sept 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 6.3.1 → 6.3.2 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 79
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 1 Oct 2026 · Analysed npm/supply-chain-guard@6.4.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 | homeofe/supply-chain-guard |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/homeofe/supply-chain-guard/.github/workflows/ci.yml@refs/tags/v6.4.0 |
| Rekor log index | 3014719834 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:470fe7d8da8e390dc0dda4a8b9afa7d3ec28427e9ee5c91c4759cff3fe75101dfb849d1c3d7ad7c5fdca93f9309dcc1aff5de387cb1548df1e5d8eb64 |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| 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 →
ioc_lookup ~309
Offline lookup against supply-chain-guard's threat intelligence and known-bad version blocklist. No network access. It always consults the bundled indicators (recent and curated ones, including every domain, url, ip and hash); package indicators older than the bundle window are in a historical catalog that is only consulted once `supply-chain-guard feed refresh` has downloaded it. Two modes: pass {ecosystem, name} to check a PACKAGE before installing/importing/recommending it, or pass {indicator} to check a single domain/url/ip/hash observed in code or logs. Returns a malicious/clean verdict with matched campaign and malware family details, and checkedAgainst.catalog says whether the catalog was consulted. Names are read the way the scanners read them: docker takes an image reference (any registry host) with the tag or sha256: digest as version; terraform and tfmodule take a registry address; swift takes the repository URL; actions takes owner/repo with the commit SHA as version.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem the name belongs to (package-mode) |
| indicator | string | – | A single domain, url, ip, or hash to look up against the feed (indicator-mode). Use INSTEAD of ecosystem/name. |
| name | string | – | Package name, e.g. 'event-stream' or '@scope/pkg' (package-mode) |
| version | string | – | Exact version to check (optional, package-mode). Without it only version-independent IOCs match. |
No output schema declared.
No examples provided.
scan_directory ~134
Run supply-chain-guard's full static malware scan (350+ detection rules: obfuscation, install hooks, C2 indicators, lockfile tampering, CI/CD abuse) over a local directory. Local filesystem only. Returns a compact JSON summary with risk score, findings count by severity, and the top findings.
| Name | Type | Req | Description |
|---|---|---|---|
| minSeverity | string | – | Only report findings at or above this severity (optional) |
| path | string | yes | Local directory path to scan |
| since | string | – | Only scan files changed since this git commit/ref (optional diff scan, e.g. 'HEAD~1' or a SHA). |
No output schema declared.
No examples provided.
scan_npm_package ~117
Scan an npm package WITHOUT installing it. NOTE: this downloads metadata and the tarball of the latest published version from the npm registry (network access). Also runs the offline IOC lookup for the given name (and exact version, if provided; the deep content scan always analyzes the latest published version).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | npm package name, e.g. 'express' or '@scope/pkg' |
| version | string | – | Exact version for the offline IOC check (optional). The remote deep scan targets the latest published version regardless. |
No output schema declared.
No examples provided.
What is the io.github.homeofe/supply-chain-guard MCP server?
io.github.homeofe/supply-chain-guard is an MCP server listed in the public MCP registry as io.github.homeofe/supply-chain-guard. Supply-chain malware scanner and MCP server: vet packages in 15 ecosystems before install, offline. This page covers its npm package (supply-chain-guard).
Is the io.github.homeofe/supply-chain-guard MCP server safe to use?
io.github.homeofe/supply-chain-guard scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 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.homeofe/supply-chain-guard MCP server expose?
io.github.homeofe/supply-chain-guard exposes 3 tools: ioc_lookup, scan_directory, scan_npm_package. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.
Is the io.github.homeofe/supply-chain-guard MCP server still maintained?
io.github.homeofe/supply-chain-guard is still listed as active in the MCP registry. We last reached this channel on 1 October 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.homeofe/supply-chain-guard MCP server under?
io.github.homeofe/supply-chain-guard declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.