@ark-ui/anatomy
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:@zag-js/presence | AI (phantom-deps): Re-exported through @zag-js dependencies; stable pattern for this anatomy package. | ai | |
| phantom-deps | phantom-dep:@zag-js/date-utils | AI (phantom-deps): Re-exported through @zag-js dependencies; stable pattern for this anatomy package. | ai | |
| phantom-deps | phantom-dep:@zag-js/color-utils | AI (phantom-deps): Re-exported through @zag-js dependencies; stable pattern for this anatomy package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 38 / 6 | |
| 3.4.0 | 37 / 6 | |
| 3.3.1 | 37 / 6 | |
| 3.3.0 | 37 / 6 | |
| 3.2.0 | 35 / 6 | |
| 3.1.0 | 35 / 6 |
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.