@electric-sql/pglite-sync
ElectricSQL Sync for PGlite
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 from manual to GitHub Actions CI publishing; confirmed by SLSA provenance attestation. Stable for this package. | ai | |
| dependencies | unvetted-dep:@electric-sql/client | AI (dependencies): First-party sibling dependency from the same @electric-sql org; expected for this package. | ai | |
| dependencies | unvetted-dep:@electric-sql/experimental | AI (dependencies): First-party sibling dependency from the same @electric-sql org; expected for this package. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.6.5 | 2 / 8 | |
| 0.6.4 | 2 / 8 | |
| 0.6.3 | 2 / 8 | |
| 0.6.2 | 2 / 8 | |
| 0.6.1 | 2 / 8 | |
| 0.6.0 | 2 / 8 | |
| 0.5.6 | 2 / 8 | |
| 0.5.5 | 2 / 8 | |
| 0.5.4 | 2 / 8 | |
| 0.5.3 | 2 / 8 | |
| 0.5.2 | 2 / 8 | |
| 0.5.1 | 2 / 8 | |
| 0.5.0 | 2 / 8 | |
| 0.4.2 | 2 / 8 | |
| 0.4.1 | 2 / 8 | |
| 0.4.0 | 2 / 8 | |
| 0.3.17 | 2 / 8 | |
| 0.3.16 | 2 / 8 | |
| 0.3.15 | 2 / 8 | |
| 0.3.14 | 2 / 8 | |
| 0.3.13 | 2 / 8 | |
| 0.3.12 | 2 / 8 | |
| 0.3.11 | 2 / 8 | |
| 0.3.10 | 2 / 8 | |
| 0.3.9 | 2 / 8 | |
| 0.3.8 | 2 / 8 | |
| 0.3.7 | 2 / 8 | |
| 0.3.6 | 2 / 7 | |
| 0.3.5 | 2 / 7 | |
| 0.3.4 | 2 / 7 | |
| 0.3.3 | 2 / 7 | |
| 0.3.2 | 2 / 7 | |
| 0.3.1 | 2 / 7 | |
| 0.3.0 | 2 / 7 | |
| 0.2.20 | 1 / 5 | |
| 0.2.19 | 1 / 5 | |
| 0.2.18 | 1 / 5 | |
| 0.2.17 | 1 / 5 | |
| 0.2.16 | 1 / 5 | |
| 0.2.14 | 1 / 5 | |
| 0.2.13 | 1 / 5 | |
| 0.2.12 | 1 / 5 | |
| 0.2.11 | 1 / 5 | |
| 0.2.10 | 1 / 5 | |
| 0.2.9 | 1 / 5 | |
| 0.2.8 | 1 / 5 | |
| 0.2.7 | 1 / 5 | |
| 0.2.6 | 1 / 5 | |
| 0.2.5 | 1 / 5 | |
| 0.2.4 | 0 / 6 | |
| 0.2.3 | 0 / 6 | |
| 0.2.2 | 0 / 6 | |
| 0.2.1 | 0 / 6 | |
| 0.2.0 | 0 / 6 |
v0.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
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.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.