@fluentui-react-native/chip
A cross-platform Chip component using the Fluent Design System. A chip is a compact representations of entities (most commonly, people) that can be typed in, deleted or dragged easily.
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): Monorepo CI metadata gap, no behavior change; publisher is trusted bot. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party sibling package in same monorepo. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/text | AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft FluentUI React Native monorepo bot publishes without Sigstore provenance; consistent across all 58 approved packages from this publisher. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/theme-tokens | AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/icon | AI (dependencies): Sibling package from the same Microsoft FluentUI React Native monorepo; expected internal dependency. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.5.5 | 8 / 18 | |
| 0.5.4 | 7 / 19 | |
| 0.5.3 | 8 / 22 | |
| 0.5.1 | 8 / 22 | |
| 0.5.0 | 8 / 22 | |
| 0.4.23 | 8 / 16 | |
| 0.4.22 | 8 / 16 | |
| 0.4.21 | 8 / 16 | |
| 0.4.20 | 8 / 16 | |
| 0.4.19 | 8 / 16 | |
| 0.4.18 | 8 / 16 | |
| 0.4.17 | 8 / 13 | |
| 0.4.16 | 8 / 13 | |
| 0.4.15 | 8 / 13 | |
| 0.4.14 | 8 / 13 | |
| 0.4.13 | 8 / 13 | |
| 0.4.12 | 8 / 13 | |
| 0.4.11 | 8 / 13 | |
| 0.4.10 | 8 / 13 | |
| 0.4.9 | 8 / 11 | |
| 0.4.8 | 8 / 9 | |
| 0.4.7 | 8 / 9 | |
| 0.4.6 | 8 / 9 | |
| 0.4.5 | 8 / 9 | |
| 0.4.4 | 8 / 9 | |
| 0.4.3 | 8 / 9 | |
| 0.4.2 | 8 / 9 | |
| 0.4.1 | 8 / 9 | |
| 0.4.0 | 8 / 9 | |
| 0.3.15 | 8 / 8 | |
| 0.3.14 | 8 / 8 | |
| 0.3.13 | 8 / 8 | |
| 0.3.12 | 8 / 8 | |
| 0.3.11 | 8 / 8 | |
| 0.3.10 | 8 / 8 | |
| 0.3.9 | 8 / 8 | |
| 0.3.8 | 8 / 8 | |
| 0.3.7 | 8 / 8 | |
| 0.3.6 | 8 / 8 | |
| 0.3.5 | 8 / 8 | |
| 0.3.4 | 8 / 8 | |
| 0.3.3 | 8 / 8 | |
| 0.3.2 | 8 / 8 | |
| 0.3.1 | 8 / 8 | |
| 0.3.0 | 8 / 8 | |
| 0.2.9 | 8 / 7 | |
| 0.2.8 | 8 / 7 | |
| 0.2.7 | 8 / 7 | |
| 0.2.6 | 8 / 7 | |
| 0.2.5 | 8 / 7 | |
| 0.2.4 | 8 / 7 | |
| 0.2.3 | 8 / 7 | |
| 0.2.2 | 8 / 7 | |
| 0.2.1 | 8 / 7 | |
| 0.2.0 | 8 / 7 | |
| 0.1.6 | 8 / 7 | |
| 0.1.5 | 8 / 7 | |
| 0.1.4 | 8 / 7 | |
| 0.1.3 | 8 / 7 | |
| 0.1.2 | 8 / 7 | |
| 0.1.1 | 8 / 7 |
v0.5.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: uifrnbot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.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.4.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.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.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
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.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.1.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.