white-web-sdk
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:taozeyu | AI (email-domain): Long-established package with 247 versions; email domain risk is latent but no evidence of active exploitation across this history. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.16.56 | 20 / 0 | |
| 2.16.55 | 20 / 0 | |
| 2.16.54 | 20 / 0 | |
| 2.16.53 | 20 / 0 | |
| 2.16.52 | 20 / 0 | |
| 2.16.51 | 20 / 0 |
v2.16.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.