@flexi-ui/button
Buttons allow users to perform actions and choose with a single tap.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@react-aria/button | AI (phantom-deps): Type/config reference only; not a real missing import for this UI component package. | ai | |
| phantom-deps | phantom-dep:@react-types/button | AI (phantom-deps): Type/config reference only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@react-types/shared | AI (phantom-deps): Type/config reference only; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is common and not a risk signal here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 6.0.14 | 2 / 0 | |
| 6.0.13 | 2 / 0 | |
| 6.0.12 | 2 / 0 | |
| 6.0.11 | 3 / 0 | |
| 6.0.10 | 3 / 0 | |
| 6.0.9 | 3 / 0 | |
| 6.0.8 | 3 / 0 | |
| 6.0.7 | 3 / 0 | |
| 6.0.6 | 3 / 0 | |
| 6.0.5 | 3 / 0 | |
| 6.0.4 | 3 / 0 | |
| 6.0.3 | 3 / 0 | |
| 6.0.2 | 3 / 0 | |
| 6.0.1 | 3 / 0 | |
| 6.0.0 | 3 / 0 | |
| 4.0.0 | 11 / 0 |
v6.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.