pinia-plugin-persistedstate
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Manual publish is normal for this maintainer; no provenance regression. | ai | |
| install-scripts | install-script:postinstall | FP sweep (deep/reputable): benign dev-tooling install script (git-hooks/build/codegen/playwright) on an established package with a real repo; verified. Flip to accept. | sean |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.7.1 | 1 / 33 | |
| 4.7.0 | 1 / 33 | |
| 4.6.0 | 3 / 32 | |
| 4.5.0 | 3 / 28 | |
| 4.4.1 | 3 / 28 | |
| 4.4.0 | 3 / 28 | |
| 4.3.0 | 4 / 28 | |
| 4.2.0 | 4 / 28 | |
| 4.1.3 | 4 / 28 | |
| 4.1.0 | 4 / 25 | |
| 4.0.2 | 4 / 25 | |
| 4.0.1 | 4 / 24 |
v4.2.0
2 findingsMaintainer email '[email protected]' uses domain 'praz.dev' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
2 findingsMaintainer email '[email protected]' uses domain 'praz.dev' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
2 findingsMaintainer email '[email protected]' uses domain 'praz.dev' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
2 findingsMaintainer email '[email protected]' uses domain 'praz.dev' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
2 findingsMaintainer email '[email protected]' uses domain 'praz.dev' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.