@uifabricshared/theming-ramp
Theming Library
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate Microsoft FluentUI sub-package; sparse README/keywords are typical for internal monorepo packages. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.21.3 | 3 / 10 | |
| 0.21.1 | 3 / 10 | |
| 0.21.0 | 3 / 10 | |
| 0.20.17 | 3 / 10 | |
| 0.20.16 | 3 / 10 | |
| 0.20.15 | 3 / 10 | |
| 0.20.14 | 3 / 10 | |
| 0.20.13 | 3 / 10 | |
| 0.20.12 | 3 / 10 | |
| 0.20.11 | 3 / 8 | |
| 0.20.10 | 3 / 8 | |
| 0.20.9 | 3 / 8 | |
| 0.20.8 | 3 / 8 | |
| 0.20.7 | 3 / 8 | |
| 0.20.6 | 3 / 8 | |
| 0.20.5 | 3 / 8 | |
| 0.20.4 | 3 / 8 | |
| 0.20.3 | 3 / 8 |
v0.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.