@ixo/matrix-crdt
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): Package now published via GitHub Actions CI with SLSA attestation; this is the expected automated-release pattern for this org. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.2.5 | 4 / 24 | |
| 1.2.1 | 4 / 25 | |
| 1.2.0 | 4 / 25 | |
| 1.1.0 | 4 / 25 | |
| 1.0.4 | 4 / 25 | |
| 1.0.3 | 4 / 25 |
v1.2.5
2 findingsThis version was published by a different npm account than previous versions on 2026-06-03. 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.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.