@nextui-org/system
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-types/datepicker | AI (phantom-deps): Type-only dependency for TS consumers, not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@react-aria/i18n | AI (phantom-deps): Monorepo re-export pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@react-aria/utils | AI (phantom-deps): Monorepo re-export pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@react-aria/overlays | AI (phantom-deps): Monorepo re-export pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@nextui-org/system-rsc | AI (phantom-deps): Same-org sibling package, expected pattern. | ai | |
| phantom-deps | phantom-dep:@internationalized/date | AI (phantom-deps): Monorepo re-export pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@nextui-org/react-utils | AI (phantom-deps): Same-org sibling package, expected pattern. | ai | |
| phantom-deps | phantom-dep:@react-stately/utils | AI (phantom-deps): @react-stately/utils is a declared dependency used transitively; phantom-dep heuristic fires as false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.4.6 | 8 / 0 | |
| 2.4.5 | 8 / 0 | |
| 2.4.4 | 8 / 0 | |
| 2.4.3 | 8 / 0 | |
| 2.4.2 | 8 / 0 | |
| 2.4.1 | 8 / 0 | |
| 2.4.0 | 8 / 0 | |
| 2.3.0 | 8 / 0 | |
| 2.2.6 | 7 / 0 | |
| 2.2.5 | 7 / 0 | |
| 2.2.4 | 7 / 0 | |
| 2.2.3 | 7 / 0 | |
| 2.2.2 | 7 / 0 | |
| 2.2.1 | 7 / 0 | |
| 2.2.0 | 7 / 0 |
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.