knex-pglite
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 0 / 8 | |
| 0.13.0 | 0 / 8 | |
| 0.12.1 | 0 / 8 | |
| 0.12.0 | 0 / 8 | |
| 0.11.0 | 2 / 8 | |
| 0.10.0 | 2 / 8 | |
| 0.9.9 | 2 / 8 | |
| 0.9.8 | 2 / 8 | |
| 0.9.7 | 2 / 8 | |
| 0.9.6 | 2 / 7 | |
| 0.9.5 | 2 / 7 | |
| 0.9.4 | 2 / 7 | |
| 0.9.3 | 2 / 7 | |
| 0.9.2 | 2 / 7 | |
| 0.9.1 | 2 / 7 | |
| 0.9.0 | 2 / 7 |
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.