@flexi-ui/link
Links allow users to click their way from page to page. This component is styled to resemble a hyperlink and semantically renders an <a> element.
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/link | AI (phantom-deps): @react-aria/link is a declared runtime dep used indirectly via @flexi-ui/use-aria-link; phantom-dep heuristic is a false positive here. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped UI component package; edit-distance match to 'pino' is coincidental with no impersonation intent. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 5.0.14 | 2 / 0 | |
| 5.0.13 | 2 / 0 | |
| 5.0.12 | 2 / 0 | |
| 5.0.11 | 3 / 0 | |
| 5.0.10 | 3 / 0 | |
| 5.0.9 | 3 / 0 | |
| 5.0.8 | 3 / 0 | |
| 5.0.7 | 3 / 0 | |
| 5.0.6 | 3 / 0 | |
| 5.0.5 | 3 / 0 | |
| 5.0.4 | 3 / 0 | |
| 5.0.3 | 3 / 0 | |
| 5.0.2 | 3 / 0 | |
| 5.0.1 | 3 / 0 | |
| 5.0.0 | 3 / 0 | |
| 4.0.0 | 8 / 0 | |
| 3.0.0 | 8 / 0 |
v5.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage 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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.