@fluentui-react-native/experimental-appearance-additions
A module to expose callbacks for additional traitCollection changes.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo; not a third-party or suspicious dependency. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft monorepo package; lack of Sigstore provenance is expected and not a security concern for this publisher. | ai |
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 2 / 16 | |
| 0.8.1 | 2 / 16 | |
| 0.8.0 | 2 / 16 | |
| 0.7.17 | 2 / 13 | |
| 0.7.16 | 2 / 13 | |
| 0.7.15 | 2 / 13 | |
| 0.7.14 | 2 / 13 | |
| 0.7.13 | 2 / 13 | |
| 0.7.12 | 2 / 13 | |
| 0.7.11 | 2 / 12 | |
| 0.7.10 | 2 / 12 | |
| 0.7.9 | 2 / 12 | |
| 0.7.8 | 2 / 12 | |
| 0.7.7 | 2 / 12 | |
| 0.7.6 | 2 / 12 | |
| 0.7.5 | 2 / 12 | |
| 0.7.4 | 2 / 12 | |
| 0.7.3 | 2 / 9 | |
| 0.7.2 | 2 / 8 | |
| 0.7.1 | 2 / 8 | |
| 0.7.0 | 2 / 8 | |
| 0.6.11 | 2 / 7 | |
| 0.6.10 | 2 / 7 | |
| 0.6.9 | 1 / 7 | |
| 0.6.8 | 1 / 7 | |
| 0.6.7 | 1 / 7 | |
| 0.6.6 | 1 / 7 | |
| 0.6.5 | 1 / 7 | |
| 0.6.4 | 1 / 7 | |
| 0.6.3 | 1 / 7 | |
| 0.6.2 | 1 / 7 | |
| 0.6.1 | 1 / 7 | |
| 0.6.0 | 1 / 7 | |
| 0.5.12 | 1 / 6 | |
| 0.5.11 | 1 / 6 | |
| 0.5.10 | 1 / 6 | |
| 0.5.9 | 1 / 6 | |
| 0.5.8 | 1 / 6 | |
| 0.5.7 | 1 / 6 | |
| 0.5.6 | 1 / 6 | |
| 0.5.5 | 1 / 6 | |
| 0.5.4 | 1 / 6 | |
| 0.5.3 | 1 / 6 | |
| 0.5.2 | 1 / 6 | |
| 0.5.1 | 1 / 6 | |
| 0.5.0 | 0 / 7 | |
| 0.4.2 | 0 / 8 | |
| 0.4.1 | 0 / 8 | |
| 0.4.0 | 0 / 8 | |
| 0.3.8 | 0 / 8 | |
| 0.3.7 | 0 / 8 | |
| 0.3.6 | 0 / 8 | |
| 0.3.5 | 0 / 8 | |
| 0.3.4 | 0 / 8 | |
| 0.3.3 | 0 / 8 | |
| 0.3.2 | 0 / 8 | |
| 0.3.1 | 0 / 8 | |
| 0.3.0 | 0 / 8 | |
| 0.2.4 | 0 / 8 | |
| 0.2.3 | 0 / 8 | |
| 0.2.2 | 0 / 8 | |
| 0.2.1 | 0 / 8 | |
| 0.2.0 | 0 / 7 |
v0.7.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.7.1
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.7.0
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.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
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.2.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.