@nextui-org/avatar
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/focus | AI (phantom-deps): Monorepo peer dep used indirectly via shared config. | ai | |
| phantom-deps | phantom-dep:@react-aria/utils | AI (phantom-deps): Monorepo peer dep used indirectly via shared config. | ai | |
| phantom-deps | phantom-dep:@nextui-org/use-image | AI (phantom-deps): Same-org scoped package, standard monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@nextui-org/react-utils | AI (phantom-deps): Same-org scoped package, standard monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@nextui-org/shared-utils | AI (phantom-deps): Same-org scoped package, standard monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@react-aria/interactions | AI (phantom-deps): Monorepo peer dep used indirectly via shared config. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.2.6 | 6 / 0 | |
| 2.2.5 | 6 / 0 | |
| 2.2.4 | 6 / 0 | |
| 2.2.3 | 6 / 0 | |
| 2.2.2 | 6 / 0 | |
| 2.2.1 | 6 / 0 | |
| 2.2.0 | 6 / 0 | |
| 2.1.0 | 6 / 0 | |
| 2.0.33 | 6 / 0 | |
| 2.0.32 | 6 / 0 | |
| 2.0.31 | 6 / 0 |
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.
v2.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.