@zag-js/steps
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Entire @zag-js/* monorepo publishes without provenance; consistent across all versions. | ai |
Versions (showing 100 of 110)
| Version | Deps | Published |
|---|---|---|
| 1.42.0 | 5 / 1 | |
| 1.41.2 | 5 / 1 | |
| 1.41.1 | 5 / 1 | |
| 1.41.0 | 5 / 1 | |
| 1.40.0 | 5 / 1 | |
| 1.39.1 | 5 / 1 | |
| 1.39.0 | 5 / 1 | |
| 1.38.2 | 5 / 1 | |
| 1.38.1 | 5 / 1 | |
| 1.38.0 | 5 / 1 | |
| 1.37.0 | 5 / 1 | |
| 1.36.0 | 5 / 1 | |
| 1.35.3 | 5 / 1 | |
| 1.35.2 | 5 / 1 | |
| 1.35.1 | 5 / 1 | |
| 1.35.0 | 5 / 1 | |
| 1.34.1 | 5 / 1 | |
| 1.34.0 | 5 / 1 | |
| 1.33.1 | 5 / 1 | |
| 1.33.0 | 5 / 1 | |
| 1.32.0 | 5 / 1 | |
| 1.31.1 | 5 / 1 | |
| 1.31.0 | 5 / 1 | |
| 1.30.0 | 5 / 1 | |
| 1.29.1 | 5 / 1 | |
| 1.29.0 | 5 / 1 | |
| 1.28.0 | 5 / 1 | |
| 1.27.1 | 5 / 1 | |
| 1.27.0 | 5 / 1 | |
| 1.26.5 | 5 / 1 | |
| 1.26.4 | 5 / 1 | |
| 1.26.3 | 5 / 1 | |
| 1.26.2 | 5 / 1 | |
| 1.26.1 | 5 / 1 | |
| 1.26.0 | 5 / 1 | |
| 1.25.0 | 5 / 1 | |
| 1.24.2 | 5 / 1 | |
| 1.24.1 | 5 / 1 | |
| 1.24.0 | 5 / 1 | |
| 1.23.0 | 5 / 1 | |
| 1.22.1 | 5 / 1 | |
| 1.22.0 | 5 / 1 | |
| 1.21.9 | 5 / 1 | |
| 1.21.8 | 5 / 1 | |
| 1.21.7 | 5 / 1 | |
| 1.21.6 | 5 / 1 | |
| 1.21.5 | 5 / 1 | |
| 1.21.4 | 5 / 1 | |
| 1.21.3 | 5 / 1 | |
| 1.21.2 | 5 / 1 | |
| 1.21.1 | 5 / 1 | |
| 1.21.0 | 5 / 1 | |
| 1.20.1 | 5 / 1 | |
| 1.20.0 | 5 / 1 | |
| 1.19.0 | 5 / 1 | |
| 1.18.5 | 5 / 1 | |
| 1.18.4 | 5 / 1 | |
| 1.18.3 | 5 / 1 | |
| 1.18.2 | 5 / 1 | |
| 1.18.1 | 5 / 1 | |
| 1.18.0 | 5 / 1 | |
| 1.17.4 | 5 / 1 | |
| 1.17.3 | 5 / 1 | |
| 1.17.2 | 5 / 1 | |
| 1.17.1 | 5 / 1 | |
| 1.17.0 | 5 / 1 | |
| 1.16.0 | 5 / 1 | |
| 1.15.7 | 5 / 1 | |
| 1.15.6 | 5 / 1 | |
| 1.15.5 | 5 / 1 | |
| 1.15.4 | 5 / 1 | |
| 1.15.3 | 5 / 1 | |
| 1.15.2 | 5 / 1 | |
| 1.15.1 | 5 / 1 | |
| 1.15.0 | 5 / 1 | |
| 1.14.0 | 5 / 1 | |
| 1.13.1 | 5 / 1 | |
| 1.13.0 | 5 / 1 | |
| 1.12.4 | 5 / 1 | |
| 1.12.3 | 5 / 1 | |
| 1.12.2 | 5 / 1 | |
| 1.12.1 | 5 / 1 | |
| 1.12.0 | 5 / 1 | |
| 1.11.0 | 5 / 1 | |
| 1.10.0 | 5 / 1 | |
| 1.9.3 | 5 / 1 | |
| 1.9.2 | 5 / 1 | |
| 1.9.1 | 5 / 1 | |
| 1.9.0 | 5 / 1 | |
| 1.8.2 | 5 / 1 | |
| 1.8.1 | 5 / 1 | |
| 1.8.0 | 5 / 1 | |
| 1.7.0 | 5 / 1 | |
| 1.6.2 | 5 / 1 | |
| 1.6.1 | 5 / 1 | |
| 1.6.0 | 5 / 1 | |
| 1.5.0 | 5 / 1 | |
| 1.4.2 | 5 / 1 | |
| 1.4.1 | 5 / 1 | |
| 1.4.0 | 5 / 1 |
v1.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.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.10.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.9.3
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.9.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.9.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.9.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.8.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.8.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.8.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.7.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.6.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.6.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.6.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.5.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.4.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.4.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.4.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.