@zauru-sdk/types
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 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 6.7.0 | 0 / 1 | |
| 6.6.0 | 0 / 1 | |
| 6.5.0 | 0 / 1 | |
| 6.4.0 | 0 / 1 | |
| 6.3.0 | 0 / 1 | |
| 6.0.0 | 0 / 1 | |
| 2.32.3 | 0 / 1 | |
| 2.32.2 | 0 / 1 | |
| 2.32.0 | 0 / 1 | |
| 2.30.0 | 0 / 1 | |
| 2.27.0 | 0 / 1 | |
| 2.16.0 | 0 / 1 | |
| 2.15.1 | 0 / 1 | |
| 2.14.1 | 0 / 1 | |
| 2.14.0 | 0 / 1 | |
| 2.7.0 | 0 / 1 | |
| 2.6.0 | 0 / 1 | |
| 2.5.0 | 0 / 1 | |
| 2.3.1 | 0 / 1 | |
| 2.2.0 | 0 / 1 | |
| 2.1.1 | 0 / 1 | |
| 2.1.0 | 0 / 1 | |
| 2.0.229 | 0 / 1 | |
| 2.0.225 | 0 / 1 | |
| 2.0.224 | 0 / 1 | |
| 2.0.223 | 0 / 1 | |
| 2.0.221 | 0 / 1 | |
| 2.0.220 | 0 / 1 | |
| 2.0.218 | 0 / 1 | |
| 2.0.217 | 0 / 1 | |
| 2.0.210 | 0 / 1 | |
| 2.0.209 | 0 / 1 | |
| 2.0.208 | 0 / 1 | |
| 2.0.207 | 0 / 1 | |
| 2.0.204 | 0 / 1 | |
| 2.0.203 | 0 / 1 | |
| 2.0.197 | 0 / 1 | |
| 2.0.196 | 0 / 1 | |
| 2.0.187 | 0 / 1 | |
| 2.0.186 | 0 / 1 | |
| 2.0.177 | 0 / 1 | |
| 2.0.176 | 0 / 1 | |
| 2.0.173 | 0 / 1 | |
| 2.0.172 | 0 / 1 | |
| 2.0.171 | 0 / 1 | |
| 2.0.170 | 0 / 1 | |
| 2.0.164 | 0 / 1 | |
| 2.0.162 | 0 / 1 | |
| 2.0.160 | 0 / 1 | |
| 2.0.154 | 0 / 1 | |
| 2.0.152 | 0 / 1 | |
| 2.0.109 | 0 / 1 | |
| 2.0.92 | 0 / 1 | |
| 2.0.89 | 0 / 1 | |
| 2.0.88 | 0 / 1 | |
| 2.0.87 | 0 / 1 | |
| 2.0.85 | 0 / 1 | |
| 2.0.84 | 0 / 1 | |
| 2.0.78 | 0 / 1 | |
| 2.0.70 | 0 / 1 | |
| 2.0.51 | 0 / 1 | |
| 2.0.50 | 0 / 1 | |
| 2.0.44 | 0 / 1 | |
| 2.0.40 | 0 / 1 | |
| 2.0.34 | 0 / 1 | |
| 2.0.33 | 0 / 1 | |
| 2.0.24 | 0 / 1 | |
| 2.0.23 | 0 / 1 | |
| 2.0.22 | 0 / 1 | |
| 2.0.21 | 0 / 1 | |
| 2.0.18 | 0 / 1 | |
| 2.0.16 | 0 / 1 | |
| 2.0.13 | 0 / 1 | |
| 2.0.10 | 0 / 1 | |
| 2.0.7 | 0 / 1 | |
| 2.0.4 | 0 / 1 | |
| 2.0.3 | 0 / 1 | |
| 2.0.0 | 0 / 1 |
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.154
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.