@composio/core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/tool.types-CNYy-lBq.d.mts | AI (source-diff): Bundled TypeScript declaration file (.d.mts) with long type-export lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/composio-CwcLLO7C.d.mts | AI (source-diff): Bundled TypeScript declaration file (.d.mts) with long type-export lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/customTool.types-BL_z-C_B.d.mts | AI (source-diff): Bundled TypeScript declaration file (.d.mts) with long type-export lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/composio-B75SFMkx.d.cts | AI (source-diff): Bundled TypeScript declaration file (.d.cts) with long type-export lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/customTool.types-2DhEI1vs.d.cts | AI (source-diff): Bundled TypeScript declaration file (.d.cts) with long type-export lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/tool.types-BlXcjUs1.d.cts | AI (source-diff): Bundled TypeScript declaration file (.d.cts) with long type-export lines; not obfuscated code. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): @types/json-schema is a type-only dep used at compile time; not directly imported at runtime by convention. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @composio/core is the Composio platform SDK, not a typosquat of cors; scoped namespace makes this a stable false positive. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 8 / 8 | |
| 0.8.0 | 8 / 8 | |
| 0.6.11 | 8 / 8 | |
| 0.6.10 | 8 / 8 | |
| 0.6.9 | 8 / 8 | |
| 0.6.8 | 8 / 8 | |
| 0.5.3 | 8 / 8 | |
| 0.4.0 | 9 / 9 | |
| 0.3.4 | 9 / 8 | |
| 0.3.0 | 9 / 8 | |
| 0.1.27 | 9 / 6 |
v0.8.1
8 findingsThis version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.