@zowe/zos-jobs-for-zowe-sdk
Zowe SDK to interact with jobs on z/OS
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 8.32.2 | 1 / 3 | |
| 8.32.0 | 1 / 3 | |
| 8.31.5 | 1 / 3 | |
| 8.31.3 | 1 / 3 | |
| 8.31.2 | 1 / 3 | |
| 8.31.1 | 1 / 3 | |
| 8.31.0 | 1 / 3 | |
| 8.30.4 | 1 / 3 | |
| 8.30.2 | 1 / 3 | |
| 8.30.1 | 1 / 3 | |
| 8.30.0 | 1 / 3 | |
| 8.29.13 | 1 / 3 | |
| 8.29.11 | 1 / 3 | |
| 8.29.10 | 1 / 3 | |
| 8.29.9 | 1 / 3 | |
| 8.29.8 | 1 / 3 | |
| 8.29.7 | 1 / 3 | |
| 8.29.6 | 1 / 3 | |
| 8.29.4 | 1 / 3 | |
| 8.29.1 | 1 / 3 | |
| 8.28.0 | 1 / 3 | |
| 8.27.4 | 1 / 3 | |
| 8.27.3 | 1 / 3 | |
| 8.27.2 | 1 / 3 | |
| 8.27.1 | 1 / 3 | |
| 8.27.0 | 1 / 3 | |
| 8.26.2 | 1 / 3 | |
| 8.26.0 | 1 / 3 | |
| 8.25.0 | 1 / 3 | |
| 8.24.6 | 1 / 3 | |
| 8.24.5 | 1 / 3 | |
| 8.24.2 | 1 / 3 | |
| 8.24.1 | 1 / 3 | |
| 8.24.0 | 1 / 3 | |
| 8.23.1 | 1 / 3 | |
| 8.23.0 | 1 / 3 | |
| 8.22.0 | 1 / 3 | |
| 8.21.0 | 1 / 3 | |
| 8.20.0 | 1 / 3 | |
| 7.29.25 | 1 / 3 | |
| 7.29.23 | 1 / 3 | |
| 7.29.22 | 1 / 3 | |
| 7.29.20 | 1 / 3 | |
| 7.29.19 | 1 / 3 | |
| 7.29.17 | 1 / 3 |
v8.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.29.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.29.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.29.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.29.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.29.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.