@fluentui-react-native/overflow
A cross-platform Overflow component for React Native.
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): Published by Microsoft's FluentUI React Native bot; lack of Sigstore provenance is consistent across all versions of this established package and is not a risk signal here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 2 / 19 | |
| 0.4.1 | 2 / 19 | |
| 0.4.0 | 2 / 19 | |
| 0.3.42 | 1 / 19 | |
| 0.3.41 | 1 / 19 | |
| 0.3.40 | 1 / 19 | |
| 0.3.39 | 1 / 19 | |
| 0.3.38 | 1 / 19 | |
| 0.3.37 | 1 / 19 | |
| 0.3.36 | 1 / 19 | |
| 0.3.35 | 1 / 19 | |
| 0.3.34 | 1 / 19 | |
| 0.3.33 | 2 / 15 | |
| 0.3.32 | 2 / 15 | |
| 0.3.31 | 2 / 15 | |
| 0.3.30 | 2 / 15 | |
| 0.3.29 | 2 / 15 | |
| 0.3.28 | 2 / 15 | |
| 0.3.27 | 2 / 15 | |
| 0.3.26 | 2 / 15 | |
| 0.3.25 | 2 / 15 | |
| 0.3.24 | 2 / 15 | |
| 0.3.23 | 2 / 13 |
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.42
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.3.41
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.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
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.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.