@zthun/trilean
A tri state boolean logic type.
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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.0.22 | 0 / 5 | |
| 2.0.21 | 0 / 5 | |
| 2.0.20 | 0 / 5 | |
| 2.0.19 | 0 / 5 | |
| 2.0.18 | 0 / 5 | |
| 2.0.17 | 0 / 5 | |
| 2.0.15 | 0 / 5 | |
| 2.0.14 | 0 / 5 | |
| 2.0.13 | 0 / 5 | |
| 2.0.12 | 0 / 5 | |
| 2.0.11 | 0 / 5 | |
| 2.0.10 | 0 / 5 | |
| 2.0.9 | 0 / 5 | |
| 2.0.8 | 0 / 5 | |
| 2.0.7 | 0 / 5 | |
| 2.0.6 | 0 / 4 | |
| 2.0.5 | 0 / 4 | |
| 2.0.4 | 0 / 4 | |
| 2.0.3 | 0 / 4 | |
| 2.0.2 | 0 / 4 | |
| 2.0.1 | 0 / 4 | |
| 2.0.0 | 0 / 4 |
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.