@electric-sql/client
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 1.5.24 | 1 / 22 | |
| 1.5.23 | 1 / 22 | |
| 1.5.22 | 1 / 22 | |
| 1.5.21 | 1 / 22 | |
| 1.5.20 | 1 / 22 | |
| 1.5.19 | 1 / 22 | |
| 1.5.18 | 1 / 22 | |
| 1.5.17 | 1 / 22 | |
| 1.5.16 | 1 / 22 | |
| 1.5.15 | 1 / 22 | |
| 1.5.14 | 1 / 21 | |
| 1.5.13 | 1 / 21 | |
| 1.5.12 | 1 / 21 | |
| 1.5.11 | 1 / 20 | |
| 1.5.10 | 1 / 20 | |
| 1.5.9 | 1 / 20 | |
| 1.5.8 | 1 / 20 | |
| 1.5.7 | 1 / 20 | |
| 1.5.6 | 1 / 20 | |
| 1.5.5 | 1 / 20 | |
| 1.5.4 | 1 / 20 | |
| 1.5.3 | 1 / 20 | |
| 1.5.2 | 1 / 20 | |
| 1.5.1 | 1 / 20 | |
| 1.5.0 | 1 / 20 | |
| 1.4.2 | 1 / 20 | |
| 1.4.1 | 1 / 20 | |
| 1.4.0 | 1 / 20 | |
| 1.3.1 | 1 / 20 | |
| 1.3.0 | 1 / 20 | |
| 1.2.2 | 1 / 20 | |
| 1.2.1 | 1 / 20 | |
| 1.2.0 | 1 / 20 | |
| 1.1.5 | 1 / 20 | |
| 1.1.4 | 1 / 20 | |
| 1.1.3 | 1 / 20 | |
| 1.1.2 | 1 / 20 | |
| 1.1.1 | 1 / 20 | |
| 1.1.0 | 1 / 20 | |
| 1.0.14 | 1 / 20 | |
| 1.0.13 | 1 / 20 | |
| 1.0.12 | 1 / 20 | |
| 1.0.11 | 1 / 20 | |
| 1.0.10 | 1 / 20 | |
| 1.0.9 | 1 / 18 | |
| 1.0.8 | 1 / 18 | |
| 1.0.7 | 1 / 18 | |
| 1.0.6 | 1 / 18 | |
| 1.0.5 | 1 / 18 | |
| 1.0.4 | 0 / 17 | |
| 1.0.3 | 0 / 17 | |
| 1.0.2 | 0 / 17 | |
| 1.0.1 | 0 / 17 | |
| 1.0.0 | 0 / 17 |
v1.5.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.