@gravity-ui/nodekit
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 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.16.1 | 13 / 13 | |
| 2.16.0 | 13 / 12 | |
| 2.15.0 | 13 / 12 | |
| 2.14.0 | 13 / 12 | |
| 2.13.0 | 13 / 12 | |
| 2.12.1 | 13 / 12 | |
| 2.12.0 | 13 / 12 | |
| 2.11.0 | 11 / 12 | |
| 2.10.1 | 11 / 12 | |
| 2.10.0 | 11 / 12 | |
| 2.9.0 | 11 / 12 | |
| 2.8.0 | 11 / 12 | |
| 2.7.0 | 11 / 12 | |
| 2.6.3 | 11 / 12 | |
| 2.6.2 | 11 / 12 | |
| 2.6.1 | 11 / 12 | |
| 2.6.0 | 11 / 12 | |
| 2.5.0 | 11 / 12 | |
| 2.4.2 | 11 / 12 | |
| 2.4.1 | 11 / 12 | |
| 2.4.0 | 11 / 12 | |
| 2.3.1 | 11 / 12 | |
| 2.3.0 | 11 / 12 | |
| 2.2.1 | 8 / 12 | |
| 2.2.0 | 8 / 12 | |
| 2.1.0 | 8 / 12 | |
| 2.0.0 | 8 / 12 |
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
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.