← Home

@mappies/miniwat-provider-openai

OpenAI provider for Miniwat

8
Versions
PolyForm-Noncommercial-1.0.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mappies

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 findings
HIGH Publisher changed: mappies → GitLab CI/CD (on 2026-05-01) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: mappies → GitLab CI/CD (on 2026-05-01) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: mappies → GitHub Actions (on 2026-04-28) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

2 findings
HIGH Publisher changed: mappies → GitHub Actions (on 2026-04-26) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

2 findings
HIGH Publisher changed: mappies → GitHub Actions (on 2026-04-24) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

2 findings
HIGH Publisher changed: mappies → GitHub Actions (on 2026-04-23) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.