@ark-ui/svelte
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@zag-js/core | AI (phantom-deps): Re-exported @zag-js dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@zag-js/time-picker | AI (phantom-deps): Re-exported @zag-js dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@zag-js/angle-slider | AI (phantom-deps): Re-exported @zag-js dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@internationalized/date | AI (phantom-deps): Re-exported dependency; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@zag-js/auto-resize | AI (phantom-deps): Same pattern — component-level usage not detected by top-level import scan. | ai | |
| phantom-deps | phantom-dep:@zag-js/cascade-select | AI (phantom-deps): Same pattern — component-level usage not detected by top-level import scan. | ai | |
| phantom-deps | phantom-dep:@zag-js/date-utils | AI (phantom-deps): Monorepo component library declares all @zag-js/* as deps; not all are directly imported at top level. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 5.22.1 | 67 / 27 | |
| 5.22.0 | 67 / 27 | |
| 5.21.2 | 67 / 27 | |
| 5.21.1 | 67 / 27 | |
| 5.21.0 | 67 / 27 | |
| 5.20.0 | 66 / 27 | |
| 5.19.1 | 65 / 27 | |
| 5.19.0 | 65 / 27 | |
| 5.18.0 | 65 / 27 | |
| 5.17.0 | 65 / 27 | |
| 5.16.0 | 64 / 27 | |
| 5.15.0 | 64 / 26 | |
| 5.14.1 | 63 / 26 | |
| 5.14.0 | 63 / 26 | |
| 5.13.0 | 63 / 26 | |
| 5.12.1 | 62 / 26 | |
| 5.12.0 | 62 / 26 | |
| 5.11.2 | 61 / 26 | |
| 5.11.1 | 61 / 26 | |
| 5.11.0 | 61 / 25 | |
| 5.10.1 | 61 / 24 | |
| 5.9.1 | 60 / 24 | |
| 5.9.0 | 60 / 24 | |
| 5.8.0 | 61 / 24 | |
| 5.7.0 | 61 / 21 | |
| 5.6.0 | 61 / 21 | |
| 5.5.0 | 60 / 21 | |
| 5.4.0 | 60 / 21 | |
| 5.3.4 | 59 / 21 | |
| 5.3.3 | 59 / 21 | |
| 5.3.2 | 59 / 21 | |
| 5.3.1 | 59 / 20 | |
| 5.3.0 | 59 / 20 | |
| 5.2.0 | 58 / 20 | |
| 5.1.1 | 58 / 20 | |
| 5.1.0 | 58 / 20 | |
| 5.0.5 | 58 / 20 | |
| 5.0.4 | 58 / 20 | |
| 5.0.3 | 58 / 20 | |
| 5.0.2 | 58 / 20 | |
| 5.0.1 | 58 / 19 | |
| 5.0.0 | 58 / 19 |
v5.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
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.1
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
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.