@nextui-org/accordion
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/dom-animation | AI (phantom-deps): Same-org monorepo sibling, newly added dep. | ai | |
| phantom-deps | phantom-dep:@react-aria/focus | AI (phantom-deps): Monorepo sibling dep, used via re-exports. | ai | |
| phantom-deps | phantom-dep:@react-aria/utils | AI (phantom-deps): Monorepo sibling dep, used via re-exports. | ai | |
| phantom-deps | phantom-dep:@react-aria/button | AI (phantom-deps): Monorepo sibling dep, used via re-exports. | ai | |
| phantom-deps | phantom-dep:@nextui-org/divider | AI (phantom-deps): Same-org monorepo sibling. | ai | |
| phantom-deps | phantom-dep:@react-stately/tree | AI (phantom-deps): Monorepo sibling dep, used via re-exports. | ai | |
| phantom-deps | phantom-dep:@react-types/shared | AI (phantom-deps): Type-only dep, expected to not be directly imported. | ai | |
| phantom-deps | phantom-dep:@nextui-org/aria-utils | AI (phantom-deps): Same-org monorepo sibling. | ai | |
| phantom-deps | phantom-dep:@react-types/accordion | AI (phantom-deps): Type-only dep, expected to not be directly imported. | ai | |
| phantom-deps | phantom-dep:@nextui-org/react-utils | AI (phantom-deps): Same-org monorepo sibling. | ai | |
| phantom-deps | phantom-dep:@nextui-org/framer-utils | AI (phantom-deps): Same-org monorepo sibling. | ai | |
| phantom-deps | phantom-dep:@nextui-org/shared-icons | AI (phantom-deps): Same-org monorepo sibling. | ai | |
| phantom-deps | phantom-dep:@nextui-org/shared-utils | AI (phantom-deps): Same-org monorepo sibling. | ai | |
| phantom-deps | phantom-dep:@react-aria/interactions | AI (phantom-deps): Monorepo sibling dep, used via re-exports. | ai | |
| phantom-deps | phantom-dep:@nextui-org/use-aria-accordion | AI (phantom-deps): Same-org monorepo sibling. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.2.7 | 15 / 0 | |
| 2.2.6 | 15 / 0 | |
| 2.2.5 | 15 / 0 | |
| 2.2.4 | 15 / 0 | |
| 2.2.3 | 15 / 0 | |
| 2.2.2 | 15 / 0 | |
| 2.2.1 | 15 / 0 | |
| 2.2.0 | 15 / 0 | |
| 2.1.0 | 15 / 0 | |
| 2.0.40 | 14 / 0 | |
| 2.0.39 | 14 / 0 | |
| 2.0.38 | 14 / 0 | |
| 2.0.37 | 14 / 0 | |
| 2.0.36 | 14 / 0 |
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.39
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.