@uifabricshared/foundation-tokens
Core tokens package
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Microsoft-published monorepo package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.16.3 | 4 / 17 | |
| 0.16.1 | 4 / 17 | |
| 0.16.0 | 4 / 17 | |
| 0.15.17 | 4 / 13 | |
| 0.15.16 | 4 / 13 | |
| 0.15.15 | 4 / 13 | |
| 0.15.14 | 4 / 13 | |
| 0.15.13 | 4 / 13 | |
| 0.15.12 | 4 / 13 | |
| 0.15.11 | 3 / 10 | |
| 0.15.10 | 3 / 10 | |
| 0.15.9 | 3 / 10 | |
| 0.15.8 | 3 / 10 | |
| 0.15.7 | 3 / 10 | |
| 0.15.6 | 3 / 11 | |
| 0.15.5 | 3 / 11 | |
| 0.15.4 | 3 / 11 | |
| 0.15.3 | 3 / 9 |
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.