@stackpress/inquire-pglite
Generic typed 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all stackpress packages; not a security signal for this org. | ai |
Versions (showing 87 of 87)
| Version | Deps | Published |
|---|---|---|
| 0.10.7 | 1 / 10 | |
| 0.10.6 | 1 / 10 | |
| 0.10.5 | 1 / 10 | |
| 0.10.4 | 1 / 10 | |
| 0.10.3 | 1 / 10 | |
| 0.10.1 | 1 / 10 | |
| 0.9.2 | 1 / 10 | |
| 0.9.1 | 1 / 10 | |
| 0.8.3 | 1 / 10 | |
| 0.8.2 | 1 / 10 | |
| 0.8.1 | 1 / 10 | |
| 0.7.2 | 1 / 10 | |
| 0.7.1 | 1 / 10 | |
| 0.6.14 | 1 / 10 | |
| 0.6.12 | 1 / 10 | |
| 0.6.11 | 1 / 10 | |
| 0.6.10 | 1 / 10 | |
| 0.6.9 | 1 / 10 | |
| 0.6.8 | 1 / 10 | |
| 0.6.7 | 1 / 10 | |
| 0.6.6 | 1 / 10 | |
| 0.6.5 | 1 / 10 | |
| 0.6.4 | 1 / 10 | |
| 0.6.2 | 1 / 10 | |
| 0.6.1 | 1 / 10 | |
| 0.5.30 | 1 / 10 | |
| 0.5.29 | 1 / 10 | |
| 0.5.28 | 1 / 10 | |
| 0.5.27 | 1 / 10 | |
| 0.5.26 | 1 / 10 | |
| 0.5.25 | 1 / 10 | |
| 0.5.24 | 1 / 10 | |
| 0.5.23 | 1 / 10 | |
| 0.5.22 | 1 / 10 | |
| 0.5.19 | 1 / 10 | |
| 0.5.17 | 1 / 10 | |
| 0.5.16 | 1 / 10 | |
| 0.5.15 | 1 / 10 | |
| 0.5.14 | 1 / 10 | |
| 0.5.12 | 1 / 10 | |
| 0.5.11 | 1 / 10 | |
| 0.5.10 | 1 / 9 | |
| 0.5.9 | 1 / 9 | |
| 0.5.8 | 1 / 9 | |
| 0.5.7 | 1 / 9 | |
| 0.5.6 | 1 / 9 | |
| 0.5.5 | 1 / 9 | |
| 0.5.4 | 1 / 9 | |
| 0.5.1 | 1 / 9 | |
| 0.4.10 | 1 / 9 | |
| 0.4.6 | 1 / 9 | |
| 0.4.5 | 1 / 9 | |
| 0.4.4 | 1 / 9 | |
| 0.4.3 | 1 / 9 | |
| 0.4.2 | 1 / 9 | |
| 0.4.1 | 1 / 9 | |
| 0.3.36 | 1 / 9 | |
| 0.3.34 | 1 / 9 | |
| 0.3.33 | 1 / 9 | |
| 0.3.32 | 1 / 9 | |
| 0.3.31 | 1 / 9 | |
| 0.3.30 | 1 / 9 | |
| 0.3.29 | 1 / 9 | |
| 0.3.28 | 1 / 9 | |
| 0.3.27 | 1 / 9 | |
| 0.3.26 | 1 / 9 | |
| 0.3.25 | 1 / 9 | |
| 0.3.24 | 1 / 9 | |
| 0.3.23 | 1 / 9 | |
| 0.3.21 | 1 / 9 | |
| 0.3.17 | 1 / 10 | |
| 0.3.16 | 1 / 10 | |
| 0.3.15 | 1 / 10 | |
| 0.2.12 | 1 / 10 | |
| 0.2.11 | 1 / 10 | |
| 0.2.10 | 1 / 10 | |
| 0.2.9 | 1 / 10 | |
| 0.2.8 | 1 / 10 | |
| 0.2.6 | 1 / 10 | |
| 0.2.5 | 1 / 10 | |
| 0.2.4 | 1 / 10 | |
| 0.2.3 | 1 / 10 | |
| 0.2.2 | 1 / 10 | |
| 0.2.1 | 1 / 10 | |
| 0.1.3 | 1 / 10 | |
| 0.1.2 | 1 / 4 | |
| 0.1.1 | 1 / 4 |
v0.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.