@uifabricshared/themed-settings
Package which drives custom cacheable settings for a component
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
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.13.3 | 2 / 11 | |
| 0.13.1 | 2 / 11 | |
| 0.13.0 | 2 / 11 | |
| 0.12.11 | 2 / 11 | |
| 0.12.10 | 2 / 9 | |
| 0.12.9 | 2 / 9 | |
| 0.12.8 | 2 / 9 | |
| 0.12.7 | 2 / 9 | |
| 0.12.6 | 2 / 9 | |
| 0.12.5 | 1 / 10 | |
| 0.12.4 | 1 / 10 | |
| 0.12.3 | 1 / 10 | |
| 0.12.2 | 1 / 10 |
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.