@mappies/miniwat-provider-openai
OpenAI provider for Miniwat
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher is GitLab CI/CD with SLSA attestation; pipeline-based publishing is the expected pattern for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added deps (openai, @mappies/miniwat-api-core, @mappies/miniwat-mcp-core) are semantically correct for an OpenAI provider; no suspicious packages. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions; no-provenance is common and no other risk signals present. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 3 / 4 | |
| 0.6.0 | 3 / 4 | |
| 0.5.0 | 3 / 4 | |
| 0.4.0 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.0 | 3 / 4 | |
| 0.1.0 | 3 / 4 | |
| 0.0.1 | 0 / 0 |
v0.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.