@flowlib/mcp
MCP (Model Context Protocol) plugin for Flowlib — exposes flow building, editing, execution, and debugging as MCP tools for Claude Desktop, VS Code Copilot, and other MCP clients
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @flowlib/mcp is a scoped MCP plugin, not a typosquat of yup; Levenshtein match is coincidental. | ai | |
| dependencies | unvetted-dep:@flowlib/core | AI (dependencies): @flowlib/core is an internal sibling package from the same flowlib monorepo/org. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.8 | 4 / 4 | |
| 0.0.7 | 4 / 4 | |
| 0.0.6 | 4 / 4 | |
| 0.0.5 | 4 / 4 | |
| 0.0.3 | 4 / 4 | |
| 0.0.2 | 4 / 4 | |
| 0.0.1 | 4 / 4 |
v0.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.