@fluentui/react-accordion
Fluent UI accordion 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is the official CSS-in-JS engine for Fluent UI, maintained by Microsoft. A stable, expected dependency for all @fluentui/* components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-aria | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion-components-preview | AI (dependencies): First-party Microsoft FluentUI monorepo sibling package; expected dependency for this component. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Microsoft FluentUI monorepo component; minimal README and no keywords are common in large monorepo component packages, not indicative of spam. | ai | |
| provenance | no-provenance | AI (provenance): Well-established Microsoft package published via uifabricteam; lack of Sigstore provenance is common and not a risk signal for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 9.12.0 | 12 / 0 | |
| 9.11.0 | 12 / 0 | |
| 9.10.0 | 12 / 0 | |
| 9.9.2 | 12 / 0 | |
| 9.9.1 | 12 / 0 | |
| 9.9.0 | 12 / 0 | |
| 9.8.16 | 12 / 0 | |
| 9.8.15 | 12 / 4 | |
| 9.8.14 | 12 / 4 | |
| 9.8.13 | 12 / 4 | |
| 9.8.12 | 12 / 4 | |
| 9.8.11 | 12 / 4 | |
| 9.8.10 | 12 / 4 | |
| 9.8.9 | 12 / 4 | |
| 9.8.8 | 12 / 4 | |
| 9.8.7 | 12 / 4 | |
| 9.8.6 | 12 / 4 | |
| 9.8.5 | 12 / 4 | |
| 9.8.4 | 12 / 4 | |
| 9.8.3 | 12 / 4 | |
| 9.8.2 | 12 / 4 | |
| 9.8.1 | 12 / 4 | |
| 9.8.0 | 12 / 4 | |
| 9.7.5 | 12 / 4 | |
| 9.7.4 | 12 / 4 | |
| 9.7.3 | 12 / 4 | |
| 9.7.2 | 12 / 4 | |
| 9.7.1 | 12 / 4 | |
| 9.7.0 | 12 / 4 | |
| 9.6.10 | 12 / 4 | |
| 9.6.9 | 12 / 4 |
v9.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.10.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.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.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.8.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.8.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.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.