@microsoft/webui-linux-arm64
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Package is explicitly a platform-specific binary distribution; bundled binaries are its entire purpose. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal metadata is expected for a binary shim package; not indicative of spam or malice. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.0.19 | 0 / 0 | |
| 0.0.18 | 0 / 0 | |
| 0.0.17 | 0 / 0 | |
| 0.0.16 | 0 / 0 | |
| 0.0.15 | 0 / 0 | |
| 0.0.14 | 0 / 0 | |
| 0.0.13 | 0 / 0 | |
| 0.0.12 | 0 / 0 | |
| 0.0.11 | 0 / 0 | |
| 0.0.10 | 0 / 0 | |
| 0.0.9 | 0 / 0 | |
| 0.0.8 | 0 / 0 | |
| 0.0.7 | 0 / 0 | |
| 0.0.6 | 0 / 0 | |
| 0.0.5 | 0 / 0 | |
| 0.0.4 | 0 / 0 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.