@fluentui/react-carousel
A composable carousel component that enables pagination with minimal rerenders
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 | no-provenance | AI (provenance): Established Microsoft Fluent UI monorepo package; lack of Sigstore provenance is common and not a risk signal for this well-known publisher. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 9.9.10 | 15 / 0 | |
| 9.9.9 | 15 / 0 | |
| 9.9.8 | 15 / 0 | |
| 9.9.7 | 15 / 0 | |
| 9.9.6 | 15 / 0 | |
| 9.9.5 | 15 / 0 | |
| 9.9.4 | 15 / 0 | |
| 9.9.3 | 15 / 0 | |
| 9.9.2 | 15 / 0 | |
| 9.9.1 | 15 / 0 | |
| 9.9.0 | 15 / 5 | |
| 9.8.13 | 15 / 5 | |
| 9.8.12 | 15 / 5 | |
| 9.8.11 | 15 / 5 | |
| 9.8.10 | 15 / 5 | |
| 9.8.9 | 15 / 5 | |
| 9.8.8 | 15 / 5 | |
| 9.8.7 | 15 / 5 | |
| 9.8.6 | 15 / 5 | |
| 9.8.5 | 15 / 5 | |
| 9.8.4 | 15 / 5 | |
| 9.8.3 | 15 / 5 | |
| 9.8.2 | 15 / 5 | |
| 9.8.1 | 15 / 5 | |
| 9.8.0 | 15 / 5 | |
| 9.7.7 | 15 / 5 | |
| 9.7.6 | 15 / 5 | |
| 9.7.5 | 15 / 5 | |
| 9.7.4 | 15 / 5 | |
| 9.7.3 | 15 / 5 | |
| 9.7.2 | 15 / 5 | |
| 9.7.1 | 15 / 5 | |
| 9.7.0 | 15 / 5 | |
| 9.6.9 | 15 / 5 | |
| 9.6.8 | 15 / 5 | |
| 9.6.7 | 15 / 5 | |
| 9.6.6 | 15 / 5 | |
| 9.6.5 | 15 / 5 | |
| 9.6.4 | 15 / 5 | |
| 9.6.3 | 15 / 5 | |
| 9.6.2 | 15 / 5 | |
| 9.6.1 | 15 / 5 | |
| 9.6.0 | 15 / 5 | |
| 9.5.0 | 15 / 5 | |
| 9.4.7 | 14 / 5 | |
| 9.4.6 | 14 / 5 | |
| 9.4.5 | 14 / 5 | |
| 9.4.4 | 14 / 5 | |
| 9.4.3 | 14 / 5 | |
| 9.4.2 | 14 / 5 | |
| 9.4.1 | 14 / 5 |
v9.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
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.