Composio

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you b

Protocols & Tool Integration TypeScript Grade B Listed MIT
76.4/100
Rank #87 of 1308
Compare Composio

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade A · 4/5 signals
Last push
2026-08-25 · 0d ago
Recent change
Rank

Is Composio safe? Composio scores 76.4/100 (Grade B), ranked #87 of 1308 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.0/10; 87% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-22
Rank Moved
Rank rose 11 spots (#89 → #78)
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
94.0
Activity sub-score · out of 100
#7

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 →

Signals refreshed 2026-08-25 05:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
29.9k
Forks
4.7k
Last Push
2026-08-25
today
Commits (4 wk)
454
Downloads (7d)
103,423
npm+pypi
HN mentions (30d)
114
Open Issues
35
Rank Change
=
was #87

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

76.4 / 100 · 100.0% confidence

Composio Protocols & Tool Integration average (58 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.1 / 25
4.6 above avg 8.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
14.4 / 17
3.0 above avg 11.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.3 above avg 13.7
AdoptionLog-scaled stars · package downloads
17.4 / 20
7.1 above avg 10.3

Activity Inputs

94.0 / 100
StarsRepository reach
26.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
7.0 / 10
OpenSSF Scorecard · scanned Aug 24, 2026
Signed Commits
87%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 6
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 7
SAST 10
Security-Policy 10
Signed-Releases 0
Token-Permissions 9
Vulnerabilities 0

Is Composio safe?

Public supply-chain signals for Composio are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Composio carries less obvious unverified-evidence risk than projects with thin signals.
Does Composio publish package provenance?
No published build provenance is currently detected for Composio. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Composio have an OpenSSF Scorecard?
Composio has an OpenSSF Scorecard score of 7.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Composio actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Composio use?
Composio ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Composio's commits signed?
87% of the last 100 commits to Composio are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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.

Compare Composio head-to-head

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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 Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
medium confidence
Partial
Some package metadata matches; some source metadata is missing
Detailed evidence is not shown in the public view.
  • 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
Score 6Rank 3HVTrust 1
2026-08-22
Rank Moved
Rank rose 11 spots (#89 → #78)
2026-06-20
Rank Moved
Rank rose 10 spots (#69 → #59)
2026-06-15
Activity Score Changed
Activity score up 6pts (86 → 92)
2026-06-11
Activity Score Changed
Activity score up 5pts (87 → 92)
2026-06-10
Rank Moved
Rank dropped 10 spots (#66 → #76)
2026-06-10
Activity Score Changed
Activity score down 5pts (92 → 87)
2026-06-08
Activity Score Changed
Activity score up 6pts (86 → 92)
2026-06-07
Activity Score Changed
Activity score down 6pts (92 → 86)
2026-05-29
HVTrust Changed
HVTrust up 10.0pts (58.9 → 68.9)
2026-05-28
Activity Score Changed
Activity score up 25pts (69 → 94)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 76.4 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/composio.svg)](https://hvtracker.net/agents/composio)
HTML:
<a href="https://hvtracker.net/agents/composio"><img src="https://hvtracker.net/badge/composio.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
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.3 · Raw JSON