@supabase/mcp-server-supabase
MCP server for interacting with Supabase
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@deno/eszip | AI (dependencies): @deno/eszip is a legitimate Deno project package; its use here is consistent with the MCP server's bundling needs. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common; no security risk for this package. | ai | |
| dependencies | unvetted-dep:gqlmin | AI (dependencies): Small GraphQL minifier used by official Supabase package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@mjackson/multipart-parser | AI (dependencies): Well-known multipart parser by @mjackson; no malware indicators. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 6 / 22 | |
| 0.8.1 | 6 / 22 | |
| 0.8.0 | 6 / 22 | |
| 0.7.0 | 6 / 22 | |
| 0.6.3 | 6 / 22 | |
| 0.6.2 | 6 / 22 | |
| 0.6.1 | 7 / 21 | |
| 0.6.0 | 7 / 21 | |
| 0.5.10 | 8 / 19 | |
| 0.5.5 | 7 / 19 | |
| 0.5.4 | 7 / 19 | |
| 0.5.2 | 7 / 19 | |
| 0.5.1 | 7 / 19 | |
| 0.5.0 | 7 / 19 | |
| 0.4.5 | 7 / 18 | |
| 0.4.4 | 7 / 18 | |
| 0.4.3 | 7 / 18 | |
| 0.4.2 | 7 / 18 | |
| 0.4.1 | 6 / 18 | |
| 0.4.0 | 6 / 17 | |
| 0.3.6 | 6 / 17 | |
| 0.3.5 | 5 / 17 | |
| 0.3.4 | 5 / 14 | |
| 0.3.3 | 5 / 14 |
v0.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.