@uifabricshared/foundation-composable
Composable component building blocks
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fluentui-react-native/merge-props | AI (dependencies): Same Microsoft FluentUI React Native monorepo; stable sibling dependency across versions. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.14.3 | 2 / 6 | |
| 0.14.1 | 2 / 6 | |
| 0.14.0 | 2 / 6 | |
| 0.13.11 | 2 / 8 | |
| 0.13.10 | 2 / 7 | |
| 0.13.9 | 2 / 7 | |
| 0.13.8 | 2 / 7 | |
| 0.13.7 | 2 / 7 | |
| 0.13.6 | 2 / 7 | |
| 0.13.5 | 2 / 7 | |
| 0.13.4 | 2 / 7 | |
| 0.13.3 | 2 / 7 | |
| 0.13.2 | 2 / 7 |
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.