@equisoft/equisoft-plan-sdk-typescript
OpenAPI client for @equisoft/equisoft-plan-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by active publishing aligns with org-level SDK regeneration cadence; no malicious indicators present. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 9.53.0 | 0 / 1 | |
| 9.52.0 | 0 / 1 | |
| 9.51.0 | 0 / 1 | |
| 9.50.0 | 0 / 1 | |
| 9.49.0 | 0 / 1 | |
| 9.48.0 | 0 / 1 | |
| 9.47.0 | 0 / 1 | |
| 9.46.0 | 0 / 1 | |
| 9.45.0 | 0 / 1 | |
| 9.44.0 | 0 / 1 | |
| 9.43.0 | 0 / 1 | |
| 9.42.0 | 0 / 1 | |
| 9.41.0 | 0 / 1 | |
| 9.40.0 | 0 / 1 | |
| 9.39.0 | 0 / 1 | |
| 9.36.0 | 0 / 1 | |
| 9.35.1 | 0 / 1 | |
| 9.35.0 | 0 / 1 | |
| 9.34.0 | 0 / 1 | |
| 9.33.0 | 0 / 1 | |
| 9.32.0 | 0 / 1 | |
| 9.31.0 | 0 / 1 | |
| 9.30.0 | 0 / 1 | |
| 9.29.0 | 0 / 1 | |
| 9.28.0 | 0 / 1 | |
| 9.27.0 | 0 / 1 | |
| 9.26.0 | 0 / 1 | |
| 9.25.1 | 0 / 1 | |
| 9.25.0 | 0 / 1 | |
| 9.24.0 | 0 / 1 | |
| 9.23.0 | 0 / 1 | |
| 9.22.0 | 0 / 1 | |
| 9.21.0 | 0 / 1 | |
| 9.20.0 | 0 / 1 | |
| 9.19.0 | 0 / 1 | |
| 9.18.0 | 0 / 1 | |
| 9.17.0 | 0 / 1 | |
| 9.16.0 | 0 / 1 | |
| 9.15.0 | 0 / 1 | |
| 9.14.0 | 0 / 1 | |
| 9.13.0 | 0 / 1 | |
| 9.12.0 | 0 / 1 | |
| 9.11.0 | 0 / 1 | |
| 9.10.0 | 0 / 1 | |
| 9.9.0 | 0 / 1 | |
| 9.8.0 | 0 / 1 | |
| 9.7.0 | 0 / 1 | |
| 9.6.0 | 0 / 1 | |
| 9.5.0 | 0 / 1 | |
| 9.4.0 | 0 / 1 |
v9.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.