@zag-js/tour
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@zag-js/core | AI (dependencies): Same-monorepo sibling dependency pinned to identical version; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established zag-js monorepo package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 9 of 109)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 9 / 1 | |
| 1.3.1 | 9 / 1 | |
| 1.3.0 | 9 / 1 | |
| 1.2.1 | 9 / 1 | |
| 1.2.0 | 9 / 1 | |
| 1.1.0 | 9 / 1 | |
| 1.0.2 | 9 / 1 | |
| 1.0.1 | 9 / 1 | |
| 1.0.0 | 9 / 1 |
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.