@composio/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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Generated SDK type/resource files; expected growth for this official client. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Stainless-generated resource files, no obfuscation or exec. | ai |
Versions (showing 3 of 3)
| Version | Deps | Published |
|---|---|---|
| 0.1.0-alpha.9 | 0 / 0 | |
| 0.1.0-alpha.8 | 0 / 0 | |
| 0.1.0-alpha.74 | 0 / 0 |
v0.1.0-alpha.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0-alpha.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0-alpha.74
2 findingsThis version was published by a different npm account than previous versions on 2026-06-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.