@zenstackhq/schema
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 1 / 4 | |
| 3.7.0 | 1 / 4 | |
| 3.6.4 | 1 / 4 | |
| 3.6.3 | 1 / 4 | |
| 3.6.2 | 1 / 4 | |
| 3.6.1 | 1 / 4 | |
| 3.6.0 | 1 / 4 | |
| 3.5.6 | 1 / 3 | |
| 3.5.5 | 1 / 3 | |
| 3.5.4 | 1 / 3 | |
| 3.5.3 | 1 / 3 | |
| 3.5.2 | 1 / 3 | |
| 3.5.1 | 1 / 3 | |
| 3.5.0 | 1 / 3 | |
| 3.4.6 | 1 / 3 | |
| 3.4.5 | 1 / 3 | |
| 3.4.4 | 1 / 3 | |
| 3.4.3 | 1 / 3 | |
| 3.4.2 | 1 / 3 | |
| 3.4.1 | 1 / 3 | |
| 3.4.0 | 1 / 3 | |
| 3.3.3 | 1 / 2 | |
| 3.3.2 | 1 / 2 | |
| 3.3.1 | 1 / 2 | |
| 3.3.0 | 1 / 2 | |
| 3.2.1 | 1 / 2 | |
| 3.2.0 | 1 / 2 | |
| 3.1.1 | 1 / 2 | |
| 3.1.0 | 1 / 2 | |
| 3.0.0 | 1 / 2 |
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.