@open-mercato/ai-assistant
AI-powered chat and tool execution for Open Mercato, using MCP (Model Context Protocol) for tool discovery and execution.
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Passing process.env to a child process in an MCP client is a standard pattern, not exfiltration. | ai | |
| phantom-deps | phantom-dep:framer-motion | AI (phantom-deps): framer-motion is listed as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 11 / 9 | |
| 0.6.2 | 11 / 9 | |
| 0.6.0 | 11 / 2 | |
| 0.5.0 | 11 / 2 | |
| 0.4.10 | 10 / 2 | |
| 0.4.9 | 10 / 2 | |
| 0.4.8 | 10 / 2 | |
| 0.4.7 | 10 / 2 | |
| 0.4.6 | 10 / 2 | |
| 0.4.5 | 10 / 2 |
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: piotrkarwatka.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.