@fluentui-react-native/experimental-expander
A cross-platform Native Expander component using the Fluent Design System. Currently only implemented on windows
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Microsoft monorepo package published via automation bot; lack of Sigstore provenance is consistent across all versions and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo; not an external or untrusted dependency. | ai |
Versions (showing 51 of 165)
| Version | Deps | Published |
|---|---|---|
| 0.9.3 | 1 / 15 | |
| 0.9.1 | 1 / 15 | |
| 0.9.0 | 1 / 15 | |
| 0.8.18 | 1 / 11 | |
| 0.8.17 | 1 / 11 | |
| 0.8.16 | 1 / 11 | |
| 0.8.15 | 1 / 11 | |
| 0.8.14 | 1 / 11 | |
| 0.8.13 | 1 / 11 | |
| 0.8.12 | 1 / 10 | |
| 0.8.11 | 1 / 10 | |
| 0.8.10 | 1 / 10 | |
| 0.8.9 | 1 / 10 | |
| 0.8.8 | 1 / 10 | |
| 0.8.7 | 1 / 10 | |
| 0.8.6 | 1 / 10 | |
| 0.8.5 | 1 / 10 | |
| 0.8.4 | 1 / 9 | |
| 0.8.3 | 1 / 7 | |
| 0.8.2 | 1 / 7 | |
| 0.8.0 | 1 / 7 | |
| 0.7.13 | 1 / 6 | |
| 0.7.12 | 2 / 6 | |
| 0.7.11 | 2 / 6 | |
| 0.7.10 | 2 / 6 | |
| 0.7.9 | 2 / 6 | |
| 0.7.8 | 2 / 6 | |
| 0.7.7 | 2 / 6 | |
| 0.7.6 | 2 / 6 | |
| 0.7.5 | 2 / 6 | |
| 0.7.4 | 2 / 6 | |
| 0.7.3 | 2 / 6 | |
| 0.7.2 | 2 / 6 | |
| 0.7.1 | 2 / 6 | |
| 0.7.0 | 2 / 6 | |
| 0.6.13 | 2 / 5 | |
| 0.6.12 | 2 / 5 | |
| 0.6.11 | 2 / 5 | |
| 0.6.10 | 2 / 5 | |
| 0.6.9 | 2 / 5 | |
| 0.6.8 | 2 / 5 | |
| 0.6.7 | 2 / 5 | |
| 0.6.6 | 2 / 5 | |
| 0.6.5 | 2 / 5 | |
| 0.6.4 | 2 / 5 | |
| 0.6.3 | 2 / 5 | |
| 0.6.2 | 2 / 5 | |
| 0.6.1 | 2 / 5 | |
| 0.6.0 | 2 / 5 | |
| 0.5.28 | 2 / 6 | |
| 0.5.27 | 2 / 6 |
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.