@alpinejs/persist
Persist Alpine data across page loads
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): Transition from calebporzio to GitHub Actions CI publishing is expected for the official alpinejs org; backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects release cadence of the alpinejs monorepo, not account takeover; SLSA attestation confirms legitimate CI origin. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.15.12 | 0 / 0 | |
| 3.15.11 | 0 / 0 | |
| 3.15.10 | 0 / 0 | |
| 3.15.9 | 0 / 0 | |
| 3.15.8 | 0 / 0 | |
| 3.15.7 | 0 / 0 | |
| 3.15.6 | 0 / 0 | |
| 3.15.5 | 0 / 0 | |
| 3.15.4 | 0 / 0 | |
| 3.15.3 | 0 / 0 | |
| 3.15.2 | 0 / 0 | |
| 3.15.1 | 0 / 0 | |
| 3.15.0 | 0 / 0 |
v3.15.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.11
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.