@electric-sql/pglite-react
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.4.4 | 0 / 15 | |
| 0.4.3 | 0 / 15 | |
| 0.4.2 | 0 / 15 | |
| 0.4.1 | 0 / 15 | |
| 0.4.0 | 0 / 15 | |
| 0.3.6 | 0 / 14 | |
| 0.3.5 | 0 / 14 | |
| 0.3.4 | 0 / 14 | |
| 0.3.3 | 0 / 14 | |
| 0.3.2 | 0 / 14 | |
| 0.3.1 | 0 / 14 | |
| 0.3.0 | 0 / 14 | |
| 0.2.34 | 0 / 14 | |
| 0.2.33 | 0 / 14 | |
| 0.2.32 | 0 / 14 | |
| 0.2.31 | 0 / 14 | |
| 0.2.30 | 0 / 14 | |
| 0.2.29 | 0 / 14 | |
| 0.2.28 | 0 / 14 | |
| 0.2.27 | 0 / 14 | |
| 0.2.26 | 0 / 14 | |
| 0.2.25 | 0 / 14 | |
| 0.2.24 | 0 / 14 | |
| 0.2.23 | 0 / 14 | |
| 0.2.22 | 0 / 14 | |
| 0.2.21 | 0 / 13 | |
| 0.2.20 | 0 / 13 | |
| 0.2.19 | 0 / 13 | |
| 0.2.18 | 0 / 13 | |
| 0.2.17 | 0 / 13 | |
| 0.2.16 | 0 / 13 | |
| 0.2.15 | 0 / 13 | |
| 0.2.14 | 0 / 13 | |
| 0.2.13 | 0 / 13 | |
| 0.2.12 | 0 / 13 | |
| 0.2.11 | 0 / 13 | |
| 0.2.10 | 0 / 13 | |
| 0.2.9 | 0 / 13 | |
| 0.2.8 | 0 / 13 | |
| 0.2.7 | 0 / 13 | |
| 0.2.6 | 0 / 13 | |
| 0.2.5 | 0 / 13 | |
| 0.2.4 | 0 / 13 | |
| 0.2.3 | 0 / 13 | |
| 0.2.2 | 0 / 13 | |
| 0.2.1 | 0 / 13 | |
| 0.2.0 | 0 / 13 |
v0.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.15
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.