@nuskin/ns-util
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() executes named custom scripts from the package's own configuration object; intentional CMS plugin pattern stable across versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.10.0 | 8 / 31 | |
| 4.9.0 | 8 / 31 | |
| 4.8.1 | 8 / 31 | |
| 4.8.0 | 8 / 31 | |
| 4.7.2 | 8 / 31 | |
| 4.7.1 | 8 / 31 | |
| 4.7.0 | 8 / 31 | |
| 4.6.1 | 8 / 31 |
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.