@byu-oit-sdk/client-workday
Workday Client
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
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 6 / 13 | |
| 0.11.0 | 6 / 13 | |
| 0.10.2 | 8 / 13 | |
| 0.10.0 | 8 / 13 | |
| 0.9.0 | 8 / 13 | |
| 0.8.1 | 8 / 13 | |
| 0.8.0 | 8 / 13 | |
| 0.7.6 | 8 / 13 | |
| 0.7.5 | 8 / 13 | |
| 0.7.4 | 8 / 13 | |
| 0.7.3 | 8 / 13 | |
| 0.7.2 | 8 / 13 | |
| 0.7.1 | 8 / 13 | |
| 0.7.0 | 8 / 13 | |
| 0.6.4 | 8 / 13 | |
| 0.6.3 | 8 / 13 | |
| 0.6.2 | 8 / 13 |
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.