@powersync/op-sqlite
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance; expected for this org's CI pipeline. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 0.9.15 | 1 / 13 | |
| 0.9.14 | 1 / 13 | |
| 0.9.13 | 1 / 12 | |
| 0.9.12 | 1 / 12 | |
| 0.9.11 | 1 / 12 | |
| 0.9.10 | 1 / 12 | |
| 0.9.9 | 1 / 12 | |
| 0.9.8 | 1 / 12 | |
| 0.9.7 | 1 / 12 | |
| 0.9.6 | 1 / 12 | |
| 0.9.5 | 1 / 12 | |
| 0.9.4 | 1 / 12 | |
| 0.9.3 | 2 / 12 | |
| 0.9.2 | 2 / 12 | |
| 0.9.1 | 2 / 12 | |
| 0.9.0 | 2 / 12 | |
| 0.8.0 | 2 / 13 | |
| 0.7.18 | 2 / 13 | |
| 0.7.17 | 2 / 13 | |
| 0.7.16 | 2 / 13 | |
| 0.7.15 | 2 / 13 | |
| 0.7.14 | 2 / 13 | |
| 0.7.13 | 2 / 13 | |
| 0.7.12 | 2 / 13 | |
| 0.7.11 | 2 / 13 | |
| 0.7.10 | 2 / 13 | |
| 0.7.9 | 2 / 13 | |
| 0.7.8 | 2 / 13 | |
| 0.7.7 | 2 / 13 | |
| 0.7.6 | 2 / 13 | |
| 0.7.5 | 2 / 13 | |
| 0.7.4 | 2 / 13 | |
| 0.7.3 | 2 / 13 | |
| 0.7.2 | 2 / 13 | |
| 0.7.1 | 2 / 13 | |
| 0.7.0 | 2 / 13 | |
| 0.6.1 | 2 / 13 | |
| 0.6.0 | 2 / 13 | |
| 0.5.6 | 2 / 13 | |
| 0.5.5 | 2 / 13 | |
| 0.5.4 | 2 / 13 | |
| 0.5.3 | 2 / 13 | |
| 0.5.2 | 2 / 13 | |
| 0.5.1 | 2 / 13 | |
| 0.5.0 | 2 / 13 | |
| 0.4.1 | 2 / 13 | |
| 0.4.0 | 2 / 14 | |
| 0.3.1 | 2 / 14 | |
| 0.3.0 | 2 / 14 | |
| 0.2.1 | 2 / 14 | |
| 0.2.0 | 2 / 14 |
v0.9.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.