@nextui-org/aria-utils
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:@nextui-org/shared-utils | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nextui-org/react-rsc-utils | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@react-stately/overlays | AI (phantom-deps): Listed as direct dep in package.json; phantom-dep heuristic false positive here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.2.7 | 8 / 0 | |
| 2.2.6 | 8 / 0 | |
| 2.2.5 | 8 / 0 | |
| 2.2.4 | 8 / 0 | |
| 2.2.3 | 8 / 0 | |
| 2.2.2 | 8 / 0 | |
| 2.2.1 | 8 / 0 | |
| 2.2.0 | 8 / 0 | |
| 2.1.0 | 8 / 0 | |
| 2.0.26 | 8 / 0 | |
| 2.0.25 | 8 / 0 | |
| 2.0.24 | 8 / 0 | |
| 2.0.23 | 8 / 0 | |
| 2.0.22 | 8 / 0 | |
| 2.0.21 | 8 / 0 | |
| 2.0.20 | 8 / 0 | |
| 2.0.19 | 8 / 0 |
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.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.