@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft OSS project resuming releases under new release bot; consistent with org-level toolchain migration. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a known Microsoft release automation account; addition is expected for this org. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/merge-props | AI (dependencies): Same Microsoft FluentUI React Native monorepo; stable sibling dependency across versions. | ai |
Versions (showing 40 of 140)
| Version | Deps | Published |
|---|---|---|
| 0.6.17 | 1 / 5 | |
| 0.6.16 | 1 / 5 | |
| 0.6.15 | 1 / 5 | |
| 0.6.14 | 1 / 5 | |
| 0.6.13 | 1 / 5 | |
| 0.6.12 | 1 / 5 | |
| 0.6.11 | 1 / 5 | |
| 0.6.10 | 1 / 5 | |
| 0.6.9 | 1 / 5 | |
| 0.6.8 | 1 / 5 | |
| 0.6.7 | 1 / 5 | |
| 0.6.6 | 1 / 5 | |
| 0.6.5 | 1 / 5 | |
| 0.6.4 | 1 / 5 | |
| 0.6.3 | 1 / 5 | |
| 0.6.2 | 1 / 5 | |
| 0.6.0 | 1 / 5 | |
| 0.5.15 | 1 / 5 | |
| 0.5.14 | 1 / 5 | |
| 0.5.13 | 1 / 5 | |
| 0.5.12 | 1 / 5 | |
| 0.5.11 | 1 / 5 | |
| 0.5.10 | 1 / 5 | |
| 0.5.9 | 1 / 5 | |
| 0.5.8 | 1 / 5 | |
| 0.5.7 | 1 / 5 | |
| 0.5.6 | 1 / 5 | |
| 0.5.5 | 1 / 5 | |
| 0.5.4 | 1 / 4 | |
| 0.5.3 | 1 / 4 | |
| 0.5.2 | 1 / 4 | |
| 0.5.1 | 1 / 4 | |
| 0.5.0 | 1 / 4 | |
| 0.4.0 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.3 | 1 / 4 | |
| 0.2.2 | 1 / 4 | |
| 0.2.1 | 1 / 4 | |
| 0.2.0 | 1 / 4 | |
| 0.1.4 | 0 / 4 |
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.