pinia
Intuitive, type safe and flexible Store for Vue
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/pinia.esm-browser.prod.js | AI (source-diff): Standard minified esbuild/tsdown prod bundle with MIT banner; not obfuscation. Stable across pinia releases. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): pinia 0.0.0 is the legitimate first release of a well-known Vue.js state management library by a trusted Vue core contributor (posva). Not a throwaway malicious package. | ai | |
| dependencies | unvetted-peer-dep:vue | AI (dependencies): Vue is the expected peer dependency for a Vue state management library; runs in consumer's app as intended. | ai | |
| dependencies | unvetted-peer-dep:@vue/composition-api | AI (dependencies): Optional peer dependency for Vue 2 composition API support; appropriate for this package's scope. | ai | |
| dependencies | unvetted-dep:vue-demi | AI (dependencies): vue-demi is a legitimate compatibility layer for Vue 2/3; appropriate dependency for this package. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Pinia is the official Vue state management library; name similarity to pino (logging) is coincidental, not typosquatting. | ai |
Versions (showing 51 of 88)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 1 / 3 | |
| 4.0.1 | 1 / 3 | |
| 4.0.0 | 1 / 3 | |
| 3.0.4 | 1 / 2 | |
| 3.0.3 | 1 / 2 | |
| 3.0.2 | 1 / 2 | |
| 3.0.1 | 1 / 2 | |
| 3.0.0 | 1 / 2 | |
| 2.3.1 | 2 / 2 | |
| 2.3.0 | 2 / 2 | |
| 2.2.8 | 2 / 2 | |
| 2.2.7 | 2 / 2 | |
| 2.2.6 | 2 / 2 | |
| 2.2.5 | 2 / 2 | |
| 2.2.4 | 2 / 2 | |
| 2.2.3 | 2 / 2 | |
| 2.2.2 | 2 / 2 | |
| 2.2.1 | 2 / 2 | |
| 2.2.0 | 2 / 2 | |
| 2.1.7 | 2 / 2 | |
| 2.1.6 | 2 / 2 | |
| 2.1.5 | 2 / 2 | |
| 2.1.4 | 2 / 2 | |
| 2.1.3 | 2 / 2 | |
| 2.1.2 | 2 / 2 | |
| 2.1.1 | 2 / 2 | |
| 2.1.0 | 2 / 2 | |
| 2.0.36 | 2 / 2 | |
| 2.0.35 | 2 / 2 | |
| 2.0.34 | 2 / 2 | |
| 2.0.33 | 2 / 2 | |
| 2.0.32 | 2 / 2 | |
| 2.0.31 | 2 / 2 | |
| 2.0.30 | 2 / 2 | |
| 2.0.29 | 2 / 2 | |
| 2.0.28 | 2 / 2 | |
| 2.0.27 | 2 / 2 | |
| 2.0.26 | 2 / 2 | |
| 2.0.25 | 2 / 2 | |
| 2.0.24 | 2 / 2 | |
| 2.0.23 | 2 / 2 | |
| 2.0.22 | 2 / 2 | |
| 2.0.21 | 2 / 2 | |
| 2.0.20 | 2 / 2 | |
| 2.0.19 | 2 / 2 | |
| 2.0.18 | 2 / 2 | |
| 2.0.17 | 2 / 2 | |
| 2.0.16 | 2 / 2 | |
| 2.0.15 | 2 / 2 | |
| 2.0.14 | 2 / 2 | |
| 2.0.13 | 2 / 6 |
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (posva) on 2026-07-14, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.