supply-chain-guard

MCPattested
v6.4.0ElvatisApache-2.0Updated 5d agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
2kDownloads/wk
6GitHub stars
3Forks
5d agoLast update
Package
AuthorElvatis
LicenseApache-2.0
Version6.4.0
Sourcenpm+mcp-registry
npmsupply-chain-guard
GitHubhomeofe/supply-chain-guard
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 1e02925
Dependencies✓ 1 resolved · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv6.4.1 · 2d agoHow well does this scan work?
EvalsNone
IndexedSep 27, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged
Statically extracted from the published packagev6.4.1 · 2d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

ioc_lookupOffline lookup against supply-chain-guard's threat intelligence and known-bad

Offline lookup against supply-chain-guard's threat intelligence and known-bad

No input schema was published for this tool.

scan_directoryRun supply-chain-guard's full static malware scan (350+ detection

Run supply-chain-guard's full static malware scan (350+ detection

No input schema was published for this tool.

scan_npm_packageScan an npm package WITHOUT installing it. NOTE: this downloads

Scan an npm package WITHOUT installing it. NOTE: this downloads

No input schema was published for this tool.

3 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
securitysupply-chainmalware-detectionnpmpypicargogolangdockerterraformglasswormshai-huludscannercligithub-actionsarifsbomslsacyclonedxdevsecopsthreat-intelligencemavengradlenugetrubygemscomposervscode-extensionsbrowser-extensionshomebrewhelmlockfile
Alternatives
Comparing tool surfaces…

Tools exposed

3 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-02 — observed resolution, not a publisher declaration.

1 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Topics

Related in security