@ark-ui/react
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved from personal account to GitHub Actions CI/CD with SLSA provenance; legitimate transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with strong publisher track record; dormancy likely reflects development cycle, not takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @zag-js/navigation-menu from same trusted @zag-js family at matching version — consistent with feature addition. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 96 new files consistent with adding navigation-menu component and related dist artifacts. | ai | |
| phantom-deps | phantom-dep:@internationalized/date | AI (phantom-deps): Declared as runtime dep for date-picker component; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@zag-js/date-utils | AI (phantom-deps): First-party @zag-js dep; phantom detection is a false positive for this package's build structure. | ai | |
| phantom-deps | phantom-dep:@zag-js/cascade-select | AI (phantom-deps): First-party @zag-js dep; phantom detection is a false positive for this package's build structure. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 5.37.2 | 67 / 32 | |
| 5.37.1 | 67 / 32 | |
| 5.37.0 | 67 / 32 | |
| 5.36.2 | 67 / 32 | |
| 5.36.1 | 67 / 32 | |
| 5.36.0 | 67 / 32 | |
| 5.35.0 | 66 / 32 | |
| 5.34.1 | 65 / 32 | |
| 5.34.0 | 65 / 32 | |
| 5.33.0 | 65 / 32 | |
| 5.32.0 | 65 / 32 | |
| 5.31.0 | 64 / 32 | |
| 5.30.0 | 64 / 31 | |
| 5.29.1 | 63 / 31 | |
| 5.29.0 | 63 / 31 | |
| 5.28.0 | 63 / 31 | |
| 5.27.1 | 62 / 31 | |
| 5.27.0 | 62 / 31 | |
| 5.26.2 | 61 / 31 | |
| 5.26.1 | 61 / 31 | |
| 5.26.0 | 61 / 31 | |
| 5.25.1 | 61 / 30 | |
| 5.25.0 | 60 / 30 | |
| 5.24.1 | 60 / 30 | |
| 5.24.0 | 60 / 30 | |
| 5.23.0 | 61 / 30 | |
| 5.22.0 | 61 / 30 | |
| 5.21.0 | 61 / 30 | |
| 5.20.0 | 60 / 30 | |
| 5.19.0 | 60 / 30 | |
| 5.18.4 | 59 / 30 | |
| 5.18.3 | 59 / 30 | |
| 5.18.2 | 59 / 30 | |
| 5.18.1 | 59 / 29 | |
| 5.18.0 | 59 / 29 | |
| 5.17.0 | 58 / 29 | |
| 5.16.1 | 58 / 29 | |
| 5.16.0 | 58 / 29 | |
| 5.15.4 | 58 / 29 | |
| 5.15.3 | 58 / 29 | |
| 5.15.2 | 58 / 29 | |
| 5.15.1 | 58 / 29 | |
| 5.15.0 | 58 / 29 | |
| 5.14.2 | 58 / 29 | |
| 5.14.1 | 58 / 29 | |
| 5.14.0 | 58 / 29 | |
| 5.13.0 | 58 / 31 | |
| 5.12.0 | 58 / 31 | |
| 5.11.0 | 58 / 31 | |
| 5.10.0 | 58 / 31 | |
| 5.9.2 | 57 / 30 | |
| 5.9.1 | 57 / 30 | |
| 5.9.0 | 57 / 30 | |
| 5.8.0 | 57 / 30 | |
| 5.7.0 | 57 / 30 | |
| 5.6.0 | 56 / 31 | |
| 5.5.0 | 54 / 32 | |
| 5.4.0 | 54 / 32 | |
| 5.3.1 | 54 / 32 | |
| 5.3.0 | 53 / 32 | |
| 5.2.0 | 53 / 32 | |
| 5.1.0 | 53 / 31 | |
| 5.0.1 | 53 / 31 | |
| 5.0.0 | 53 / 31 |
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.