@fluentui-react-native/e2e-testing
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react | AI (phantom-deps): E2E testing harness; react is a declared dependency used across platform configs. | ai | |
| phantom-deps | phantom-dep:react-native | AI (phantom-deps): Platform-specific declared dependency; expected for multi-platform testing harness. | ai | |
| phantom-deps | phantom-dep:react-native-macos | AI (phantom-deps): Platform-specific declared dependency; expected for multi-platform testing harness. | ai | |
| phantom-deps | phantom-dep:react-native-windows | AI (phantom-deps): Platform-specific declared dependency; expected for multi-platform testing harness. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.43.11 | 4 / 29 | |
| 1.43.10 | 4 / 29 | |
| 1.43.9 | 4 / 29 | |
| 1.43.8 | 4 / 29 | |
| 1.43.7 | 4 / 29 | |
| 1.43.6 | 4 / 29 | |
| 1.43.5 | 4 / 29 | |
| 1.43.4 | 4 / 29 | |
| 1.43.3 | 4 / 29 | |
| 1.43.2 | 4 / 29 | |
| 1.43.1 | 4 / 29 | |
| 1.43.0 | 4 / 29 | |
| 1.42.0 | 4 / 29 | |
| 1.41.0 | 4 / 29 | |
| 1.40.9 | 4 / 29 | |
| 1.40.8 | 4 / 28 | |
| 1.40.7 | 4 / 28 | |
| 1.40.6 | 4 / 28 | |
| 1.40.5 | 4 / 28 | |
| 1.40.4 | 4 / 28 | |
| 1.40.3 | 4 / 28 | |
| 1.40.2 | 4 / 28 | |
| 1.40.1 | 4 / 28 | |
| 1.40.0 | 4 / 28 | |
| 1.39.4 | 4 / 28 | |
| 1.39.3 | 4 / 28 | |
| 1.39.2 | 4 / 28 | |
| 1.39.1 | 4 / 28 | |
| 1.39.0 | 4 / 28 |
v1.40.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.