@nuskin/product-lib
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 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.7.0 | 3 / 12 | |
| 2.6.1 | 3 / 12 | |
| 2.6.0 | 3 / 12 | |
| 2.5.0 | 3 / 12 | |
| 2.4.1 | 3 / 12 | |
| 2.4.0 | 3 / 12 | |
| 2.3.1 | 3 / 12 | |
| 2.3.0 | 3 / 12 | |
| 2.2.1 | 3 / 12 | |
| 2.2.0 | 3 / 12 | |
| 2.1.0 | 3 / 12 | |
| 2.0.10 | 3 / 12 | |
| 2.0.9 | 2 / 12 |
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.