@fluentui/react-spinbutton
Fluent UI React SpinButton 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is the official CSS-in-JS engine for Fluent UI, maintained by Microsoft. It is a legitimate and expected dependency for all @fluentui/react-* components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-field | AI (dependencies): First-party @fluentui sibling package from the Microsoft Fluent UI monorepo. Expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): First-party @fluentui sibling package from the Microsoft Fluent UI monorepo. Expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui sibling package from the Microsoft Fluent UI monorepo. Expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): First-party @fluentui sibling package from the Microsoft Fluent UI monorepo. Expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui sibling package from the Microsoft Fluent UI monorepo. Expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui sibling package from the Microsoft Fluent UI monorepo. Expected dependency for this component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui sibling package from the Microsoft Fluent UI monorepo. Expected dependency for this component. | ai | |
| provenance | no-provenance | AI (provenance): The @fluentui monorepo is a well-established Microsoft project. Lack of Sigstore provenance is common and not a meaningful risk signal for this publisher. | ai |
Versions (showing 100 of 163)
| Version | Deps | Published |
|---|---|---|
| 9.6.4 | 9 / 0 | |
| 9.6.3 | 9 / 0 | |
| 9.6.2 | 9 / 0 | |
| 9.6.1 | 9 / 0 | |
| 9.6.0 | 9 / 0 | |
| 9.5.16 | 9 / 0 | |
| 9.5.15 | 9 / 0 | |
| 9.5.14 | 9 / 0 | |
| 9.5.13 | 9 / 0 | |
| 9.5.12 | 9 / 5 | |
| 9.5.11 | 9 / 5 | |
| 9.5.10 | 9 / 5 | |
| 9.5.9 | 9 / 5 | |
| 9.5.8 | 9 / 5 | |
| 9.5.7 | 9 / 5 | |
| 9.5.6 | 9 / 5 | |
| 9.5.5 | 9 / 5 | |
| 9.5.4 | 9 / 5 | |
| 9.5.3 | 9 / 5 | |
| 9.5.2 | 9 / 5 | |
| 9.5.1 | 9 / 5 | |
| 9.5.0 | 9 / 5 | |
| 9.4.7 | 9 / 5 | |
| 9.4.6 | 9 / 5 | |
| 9.4.5 | 9 / 5 | |
| 9.4.4 | 9 / 5 | |
| 9.4.3 | 9 / 5 | |
| 9.4.2 | 9 / 5 | |
| 9.4.1 | 9 / 5 | |
| 9.4.0 | 9 / 5 | |
| 9.3.9 | 9 / 5 | |
| 9.3.8 | 9 / 5 | |
| 9.3.7 | 9 / 5 | |
| 9.3.6 | 9 / 5 | |
| 9.3.5 | 9 / 5 | |
| 9.3.4 | 9 / 5 | |
| 9.3.3 | 9 / 5 | |
| 9.3.2 | 9 / 5 | |
| 9.3.1 | 9 / 5 | |
| 9.3.0 | 9 / 5 | |
| 9.2.98 | 9 / 5 | |
| 9.2.97 | 9 / 5 | |
| 9.2.96 | 9 / 5 | |
| 9.2.95 | 9 / 5 | |
| 9.2.94 | 9 / 5 | |
| 9.2.93 | 9 / 5 | |
| 9.2.92 | 9 / 5 | |
| 9.2.91 | 9 / 5 | |
| 9.2.90 | 9 / 6 | |
| 9.2.89 | 9 / 6 | |
| 9.2.88 | 9 / 6 | |
| 9.2.87 | 9 / 6 | |
| 9.2.86 | 9 / 6 | |
| 9.2.85 | 9 / 6 | |
| 9.2.84 | 9 / 6 | |
| 9.2.83 | 9 / 6 | |
| 9.2.82 | 9 / 6 | |
| 9.2.81 | 9 / 6 | |
| 9.2.80 | 9 / 6 | |
| 9.2.79 | 9 / 6 | |
| 9.2.78 | 9 / 6 | |
| 9.2.77 | 9 / 6 | |
| 9.2.76 | 9 / 6 | |
| 9.2.75 | 9 / 6 | |
| 9.2.74 | 9 / 6 | |
| 9.2.73 | 9 / 6 | |
| 9.2.72 | 9 / 6 | |
| 9.2.71 | 9 / 6 | |
| 9.2.70 | 9 / 6 | |
| 9.2.69 | 9 / 6 | |
| 9.2.68 | 9 / 6 | |
| 9.2.67 | 9 / 6 | |
| 9.2.66 | 9 / 6 | |
| 9.2.65 | 9 / 6 | |
| 9.2.64 | 9 / 6 | |
| 9.2.63 | 9 / 6 | |
| 9.2.62 | 9 / 6 | |
| 9.2.61 | 9 / 6 | |
| 9.2.60 | 9 / 6 | |
| 9.2.59 | 9 / 6 | |
| 9.2.58 | 9 / 6 | |
| 9.2.57 | 9 / 6 | |
| 9.2.56 | 9 / 6 | |
| 9.2.55 | 9 / 6 | |
| 9.2.54 | 9 / 6 | |
| 9.2.53 | 9 / 6 | |
| 9.2.52 | 9 / 6 | |
| 9.2.51 | 9 / 6 | |
| 9.2.50 | 9 / 6 | |
| 9.2.49 | 9 / 6 | |
| 9.2.48 | 9 / 6 | |
| 9.2.47 | 9 / 6 | |
| 9.2.46 | 9 / 6 | |
| 9.2.45 | 9 / 6 | |
| 9.2.44 | 9 / 6 | |
| 9.2.43 | 9 / 6 | |
| 9.2.42 | 9 / 6 | |
| 9.2.41 | 9 / 6 | |
| 9.2.39 | 9 / 6 | |
| 9.2.38 | 9 / 6 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.73
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.72
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.71
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.70
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.69
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.68
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.67
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.66
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.65
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.64
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.63
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.62
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.61
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.60
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.59
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.58
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.57
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.56
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.55
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.54
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.53
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.52
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.51
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.50
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.49
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.48
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.47
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.46
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.45
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.44
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.43
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.42
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.41
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.39
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.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.