@fluentui-react-native/separator
A cross-platform Separator component using the Fluent Design System
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 | missing-githead | AI (provenance): High-volume Microsoft FluentUI monorepo package; missing gitHead reflects CI tooling change, not a supply-chain risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @fluentui-react-native package from the same Microsoft monorepo; not a third-party injection. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/theme-tokens | AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency, not a third-party risk. | ai |
Versions (showing 51 of 297)
| Version | Deps | Published |
|---|---|---|
| 0.19.5 | 4 / 15 | |
| 0.19.4 | 3 / 16 | |
| 0.19.3 | 3 / 20 | |
| 0.19.1 | 3 / 20 | |
| 0.19.0 | 3 / 20 | |
| 0.18.17 | 3 / 15 | |
| 0.18.16 | 3 / 15 | |
| 0.18.15 | 3 / 15 | |
| 0.18.14 | 3 / 15 | |
| 0.18.13 | 3 / 15 | |
| 0.18.12 | 3 / 15 | |
| 0.18.11 | 3 / 11 | |
| 0.18.10 | 3 / 11 | |
| 0.18.9 | 3 / 11 | |
| 0.18.8 | 3 / 11 | |
| 0.18.7 | 3 / 11 | |
| 0.18.6 | 3 / 11 | |
| 0.18.5 | 3 / 11 | |
| 0.18.4 | 3 / 11 | |
| 0.18.3 | 3 / 9 | |
| 0.18.2 | 3 / 7 | |
| 0.18.1 | 3 / 7 | |
| 0.18.0 | 3 / 7 | |
| 0.17.11 | 3 / 6 | |
| 0.17.10 | 3 / 6 | |
| 0.17.9 | 3 / 6 | |
| 0.17.8 | 3 / 6 | |
| 0.17.7 | 3 / 6 | |
| 0.17.6 | 3 / 6 | |
| 0.17.5 | 3 / 6 | |
| 0.17.4 | 3 / 6 | |
| 0.17.3 | 3 / 6 | |
| 0.17.2 | 3 / 6 | |
| 0.17.1 | 3 / 6 | |
| 0.17.0 | 3 / 6 | |
| 0.16.10 | 3 / 5 | |
| 0.16.9 | 3 / 5 | |
| 0.16.8 | 3 / 5 | |
| 0.16.7 | 3 / 5 | |
| 0.16.6 | 3 / 5 | |
| 0.16.5 | 3 / 5 | |
| 0.16.4 | 3 / 5 | |
| 0.16.3 | 3 / 5 | |
| 0.16.2 | 3 / 5 | |
| 0.16.1 | 3 / 5 | |
| 0.16.0 | 3 / 5 | |
| 0.15.0 | 3 / 5 | |
| 0.14.24 | 3 / 6 | |
| 0.14.23 | 3 / 6 | |
| 0.14.22 | 3 / 6 | |
| 0.14.21 | 3 / 6 |
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.