@equisoft/equisoft-connect-sdk-typescript
OpenAPI client for @equisoft/equisoft-connect-sdk-typescript
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 |
|---|---|---|
| 13.55.0 | 0 / 1 | |
| 13.54.0 | 0 / 1 | |
| 13.53.0 | 0 / 1 | |
| 13.52.0 | 0 / 1 | |
| 13.51.0 | 0 / 1 | |
| 13.50.0 | 0 / 1 | |
| 13.49.0 | 0 / 1 | |
| 13.48.0 | 0 / 1 | |
| 13.47.0 | 0 / 1 | |
| 13.46.0 | 0 / 1 | |
| 13.45.0 | 0 / 1 | |
| 13.44.0 | 0 / 1 | |
| 13.43.0 | 0 / 1 | |
| 13.42.0 | 0 / 1 | |
| 13.41.0 | 0 / 1 | |
| 13.40.0 | 0 / 1 | |
| 13.39.0 | 0 / 1 |
v13.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.