@uifabricshared/foundation-compose
Compose infrastructure
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): Established Microsoft OSS monorepo package published via automation bot; lack of Sigstore provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.16.3 | 8 / 9 | |
| 1.16.1 | 8 / 9 | |
| 1.16.0 | 8 / 9 | |
| 1.15.17 | 8 / 10 | |
| 1.15.16 | 8 / 10 | |
| 1.15.15 | 8 / 10 | |
| 1.15.14 | 8 / 10 | |
| 1.15.13 | 8 / 10 | |
| 1.15.12 | 8 / 10 | |
| 1.15.11 | 8 / 9 | |
| 1.15.10 | 8 / 9 | |
| 1.15.9 | 8 / 9 | |
| 1.15.8 | 8 / 9 | |
| 1.15.7 | 8 / 9 | |
| 1.15.6 | 9 / 9 | |
| 1.15.5 | 9 / 9 | |
| 1.15.4 | 9 / 9 | |
| 1.15.3 | 9 / 8 |
v1.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.