@fluentui/react-tags
Fluent UI Tag component
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:@fluentui/react-aria | AI (phantom-deps): Declared but not directly imported; common in Microsoft Fluent UI monorepo packages for transitive/peer dependency resolution. Not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft Fluent UI package published via uifabricteam; lack of Sigstore provenance is common and not a risk signal for this well-known package. | ai |
Versions (showing 100 of 110)
| Version | Deps | Published |
|---|---|---|
| 9.9.2 | 11 / 0 | |
| 9.9.1 | 11 / 0 | |
| 9.9.0 | 11 / 0 | |
| 9.8.1 | 11 / 0 | |
| 9.8.0 | 11 / 0 | |
| 9.7.19 | 11 / 0 | |
| 9.7.18 | 11 / 0 | |
| 9.7.17 | 11 / 0 | |
| 9.7.16 | 11 / 0 | |
| 9.7.15 | 11 / 0 | |
| 9.7.14 | 11 / 0 | |
| 9.7.13 | 11 / 6 | |
| 9.7.12 | 11 / 6 | |
| 9.7.11 | 11 / 6 | |
| 9.7.10 | 11 / 6 | |
| 9.7.9 | 11 / 6 | |
| 9.7.8 | 11 / 6 | |
| 9.7.7 | 11 / 6 | |
| 9.7.6 | 11 / 6 | |
| 9.7.5 | 11 / 6 | |
| 9.7.4 | 11 / 6 | |
| 9.7.3 | 11 / 6 | |
| 9.7.2 | 11 / 6 | |
| 9.7.1 | 11 / 6 | |
| 9.7.0 | 11 / 6 | |
| 9.6.7 | 11 / 6 | |
| 9.6.6 | 11 / 6 | |
| 9.6.5 | 11 / 6 | |
| 9.6.4 | 11 / 6 | |
| 9.6.3 | 11 / 6 | |
| 9.6.2 | 11 / 6 | |
| 9.6.1 | 11 / 6 | |
| 9.6.0 | 11 / 6 | |
| 9.5.7 | 11 / 6 | |
| 9.5.6 | 11 / 6 | |
| 9.5.5 | 11 / 6 | |
| 9.5.4 | 11 / 6 | |
| 9.5.3 | 11 / 6 | |
| 9.5.2 | 11 / 6 | |
| 9.5.1 | 11 / 6 | |
| 9.5.0 | 11 / 6 | |
| 9.4.1 | 11 / 6 | |
| 9.4.0 | 11 / 6 | |
| 9.3.30 | 11 / 6 | |
| 9.3.29 | 11 / 6 | |
| 9.3.28 | 11 / 6 | |
| 9.3.27 | 11 / 6 | |
| 9.3.26 | 11 / 6 | |
| 9.3.25 | 11 / 6 | |
| 9.3.24 | 11 / 6 | |
| 9.3.23 | 11 / 6 | |
| 9.3.22 | 11 / 6 | |
| 9.3.21 | 11 / 6 | |
| 9.3.20 | 11 / 7 | |
| 9.3.19 | 11 / 7 | |
| 9.3.18 | 11 / 7 | |
| 9.3.17 | 11 / 7 | |
| 9.3.16 | 11 / 7 | |
| 9.3.15 | 11 / 7 | |
| 9.3.14 | 11 / 7 | |
| 9.3.13 | 11 / 7 | |
| 9.3.12 | 11 / 7 | |
| 9.3.11 | 11 / 7 | |
| 9.3.10 | 11 / 7 | |
| 9.3.9 | 11 / 7 | |
| 9.3.8 | 11 / 6 | |
| 9.3.7 | 11 / 6 | |
| 9.3.6 | 11 / 6 | |
| 9.3.5 | 11 / 6 | |
| 9.3.4 | 11 / 6 | |
| 9.3.3 | 11 / 6 | |
| 9.3.2 | 11 / 6 | |
| 9.3.1 | 11 / 6 | |
| 9.3.0 | 11 / 6 | |
| 9.2.1 | 11 / 6 | |
| 9.2.0 | 11 / 6 | |
| 9.1.3 | 11 / 6 | |
| 9.1.2 | 11 / 6 | |
| 9.1.1 | 11 / 6 | |
| 9.1.0 | 11 / 6 | |
| 9.0.29 | 11 / 6 | |
| 9.0.28 | 11 / 6 | |
| 9.0.27 | 11 / 6 | |
| 9.0.26 | 11 / 6 | |
| 9.0.25 | 11 / 6 | |
| 9.0.24 | 11 / 6 | |
| 9.0.23 | 11 / 6 | |
| 9.0.22 | 11 / 6 | |
| 9.0.21 | 11 / 6 | |
| 9.0.20 | 11 / 6 | |
| 9.0.19 | 11 / 6 | |
| 9.0.18 | 11 / 6 | |
| 9.0.17 | 11 / 6 | |
| 9.0.16 | 11 / 6 | |
| 9.0.15 | 11 / 6 | |
| 9.0.14 | 11 / 6 | |
| 9.0.13 | 11 / 6 | |
| 9.0.12 | 11 / 6 | |
| 9.0.11 | 11 / 6 | |
| 9.0.10 | 11 / 6 |
v9.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.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.
v9.3.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.
v9.3.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.
v9.3.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.
v9.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.
v9.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.
v9.1.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.
v9.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.
v9.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.
v9.1.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.
v9.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.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.
v9.0.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.
v9.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.