@nextui-org/button
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
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/peer dependency referenced in config but not directly imported; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@react-types/button | AI (phantom-deps): Type-only dependency; phantom-dep heuristic fires on config references, not a real risk. | ai | |
| phantom-deps | phantom-dep:@react-types/shared | AI (phantom-deps): Type-only dependency; phantom-dep heuristic fires on config references, not a real risk. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.2.9 | 11 / 0 | |
| 2.2.8 | 11 / 0 | |
| 2.2.7 | 11 / 0 | |
| 2.2.6 | 11 / 0 | |
| 2.2.5 | 11 / 0 | |
| 2.2.4 | 11 / 0 | |
| 2.2.3 | 11 / 0 | |
| 2.2.2 | 11 / 0 | |
| 2.2.1 | 11 / 0 | |
| 2.2.0 | 11 / 0 | |
| 2.1.0 | 11 / 0 | |
| 2.0.38 | 11 / 0 | |
| 2.0.37 | 11 / 0 | |
| 2.0.36 | 11 / 0 | |
| 2.0.35 | 11 / 0 | |
| 2.0.34 | 11 / 0 | |
| 2.0.33 | 11 / 0 | |
| 2.0.32 | 11 / 0 |
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.