← Home

@mistralai/mistralai-gcp

npm Repository Homepage
2
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

nelson.proia.mistralaiaac228mistralai-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): SLSA provenance attestation confirms CI/CD build; publisher change appears to be a legitimate bot account transition for the official Mistral AI org. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers align with official Mistral AI org transition; SLSA attestation corroborates legitimacy. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer rotation consistent with org-level transition; no malicious indicators present. ai
source-diff large-new-source-files AI (source-diff): Major version bump (v1→v2) with SDK refactor explains 236 new files; no obfuscation or suspicious patterns flagged. ai

Versions (showing 2 of 2)

Version Deps Published
2.0.0 2 / 3
1.7.0 2 / 5

v2.0.0

2 findings
HIGH Publisher changed: aac228 → mistralai-bot (on 2026-05-25) provenance

This version was published by a different npm account than previous versions on 2026-05-25. 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/v1). This is the strongest supply chain integrity signal.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.