Composio
Website
Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Is Composio safe? Promising trust profile, but some evidence still deserves review.
Compare Composio
How does it stack up against its Protocols & Tool Integration neighbours?
Pick any agent to compare →In detail: Composio scores 74.5/100 (Grade B), ranked #247 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.2/10; 44% of recent commits are signed; no published advisory affects its latest release (composio-core); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
What Composio can reach, and who runs it
Checked 2026-10-06, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves. These facts describe the product. They don't change its score.
Who runs it
- PUBLISHER Run by Sampark Inc, doing business as Composio. Its terms are governed by Delaware law.
What it can reach
- PUBLISHER An agent using Composio can act in every app you connect, within the scopes you granted. Composio's own advice is to treat those scopes like production credentials.
Where your data goes
- PUBLISHER Composio's cloud stores the OAuth access and refresh tokens and API keys of the apps you connect, and uses them to call those apps on your behalf. Using your own OAuth app doesn't change that.
- PUBLISHER Those credentials are encrypted at rest (AES-256-GCM) with keys Composio holds by default. Customer-managed keys, a private VPC or self-hosting are enterprise arrangements.
- PUBLISHER Connected-account tokens are redacted from API responses by default, and a Zero Data Retention option stops call payloads from being stored.
Security practice
- PUBLISHER States SOC 2 Type II compliance. The report and the sub-processor list are in its trust center, trust.composio.dev. Vulnerability reports go to [email protected].
- CHECKED GitHub private vulnerability reporting is enabled on the repository, which has a SECURITY.md. composio.dev serves no security.txt.
How Composio could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +13.8 → 88.3 A · #5 of 62
- Raise the OSSF Scorecard from 7.2 to 9.0lowest checks: CII-Best-Practices 0, Signed-Releases 0, Vulnerabilities 0 +3.8 → 78.3 B · #10 of 62
- Sign every commit44% signed today +2.8 → 77.3 B · #10 of 62
Chain of custody
Scanners check what the code says. This traces who ships Composio and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/composiohq/composio, MIT, last pushed 2026-10-09. 44% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 7.2/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:
- Code Review4
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions9
- Pinned Dependencies7
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 5CI-Tests 9CII-Best-Practices 0Code-Review 4Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 10License 10Maintained 10Packaging 10Pinned-Dependencies 7SAST 7Security-Policy 10Signed-Releases 0Token-Permissions 9Vulnerabilities 0 -
Published packages Linked, not attested
- npm composio-core No source link declared No build attestation
- PyPI composio-core Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: composio-core 0.7.21. No published advisory affects it (OSV, checked 2026-10-09).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Composio.
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Composio’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Composio compares in Protocols & Tool Integration
- #9 CLI-Anything 79.3 +4.8
- #10 Pi MCP Adapter 75.9 +1.4
- #11 Composio 74.5 this agent
- #12 mcp-proxy 74.4 −0.1
- #13 Chrome DevTools MCP 74.3 −0.2
Bars show each HVTrust score; the tick marks Composio’s 74.5.
Where the 74.5 comes from
HVTrust dimensions vs the Protocols & Tool Integration average
74.5 / 100 · 100.0% confidenceComposio Protocols & Tool Integration average (62 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
94.0 / 100Common questions about Composio
Does Composio publish package provenance?
Does Composio have an OpenSSF Scorecard?
Is Composio actively maintained?
What license does Composio use?
Are Composio's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Composio?
For maintainers
HVTrust scores Composio from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/composio)
<a href="https://hvtracker.net/agents/composio"><img src="https://hvtracker.net/badge/composio.svg" alt="HVTrust"></a>
Other agents in Protocols & Tool Integration
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON