# supply-chain-guard

Open-source supply-chain security scanner, local and offline. Matches known-malicious packages, extensions, plugins, providers, container images and CI actions in 15 ecosystems, including transitive lockfile dependencies at any depth, and detects GlassWor

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 6.4.0
- **Author:** Elvatis
- **License:** Apache-2.0
- **npm:** supply-chain-guard
- **Source:** https://github.com/homeofe/supply-chain-guard
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 4 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-02T11:50:32.109Z
- **Version scanned:** 6.4.1
- **CVEs:** none found by OSV at scan time

## Tools

3 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `ioc_lookup` — Offline lookup against supply-chain-guard's threat intelligence and known-bad
- `scan_directory` — Run supply-chain-guard's full static malware scan (350+ detection
- `scan_npm_package` — Scan an npm package WITHOUT installing it. NOTE: this downloads

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"supply-chain-guard\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"supply-chain-guard\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 12, ceiling 30 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/supply-chain-guard
- Install plan: https://forgeregistry.com/api/v1/packages/supply-chain-guard/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/supply-chain-guard
- HTML page: https://forgeregistry.com/registry/supply-chain-guard
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.