Skip to main content
Back to time machine

Composio

Tracked across 18 snapshots (2026-04-09 → 2026-07-19).

Tool detailAsk about this trajectory
Latest rating
59
Rating delta
-1
Latest signal
Tracked
Tracked
Caps now applied
1

Rating timeline

02550751002026-04-09 — rating 60, Tracked2026-04-10 — rating 60, Tracked2026-04-20 — rating 65, Tracked2026-04-21 — rating 65, Tracked2026-04-30 — rating 65, Tracked2026-05-04 — rating 65, Tracked2026-05-05 — rating 65, Tracked2026-05-16 — rating 65, Tracked2026-05-18 — rating 65, Tracked2026-05-28 — rating 63, Tracked2026-06-10 — rating 59, Tracked2026-06-12 — rating 59, Tracked2026-06-26 — rating 59, Tracked2026-06-28 — rating 59, Tracked2026-06-29 — rating 59, Tracked2026-07-03 — rating 59, Tracked2026-07-13 — rating 59, Tracked2026-07-19 — rating 59, Tracked2026-04-092026-05-282026-07-19

Dimension trajectory

Autonomy

8/20
2002026-04-09 — 10/202026-04-10 — 10/202026-04-20 — 11/202026-04-21 — 11/202026-04-30 — 11/202026-05-04 — 11/202026-05-05 — 11/202026-05-16 — 11/202026-05-18 — 11/202026-05-28 — 11/202026-06-10 — 8/202026-06-12 — 8/202026-06-26 — 8/202026-06-28 — 8/202026-06-29 — 8/202026-07-03 — 8/202026-07-13 — 8/202026-07-19 — 8/20

Integration

16/20
2002026-04-09 — 13/202026-04-10 — 13/202026-04-20 — 16/202026-04-21 — 16/202026-04-30 — 16/202026-05-04 — 16/202026-05-05 — 16/202026-05-16 — 16/202026-05-18 — 16/202026-05-28 — 16/202026-06-10 — 16/202026-06-12 — 16/202026-06-26 — 16/202026-06-28 — 16/202026-06-29 — 16/202026-07-03 — 16/202026-07-13 — 16/202026-07-19 — 16/20

Context

8/20
2002026-04-09 — 9/202026-04-10 — 9/202026-04-20 — 9/202026-04-21 — 9/202026-04-30 — 9/202026-05-04 — 9/202026-05-05 — 9/202026-05-16 — 9/202026-05-18 — 9/202026-05-28 — 9/202026-06-10 — 8/202026-06-12 — 8/202026-06-26 — 8/202026-06-28 — 8/202026-06-29 — 8/202026-07-03 — 8/202026-07-13 — 8/202026-07-19 — 8/20

Compliance

11/20
2002026-04-09 — 14/202026-04-10 — 14/202026-04-20 — 14/202026-04-21 — 14/202026-04-30 — 14/202026-05-04 — 14/202026-05-05 — 14/202026-05-16 — 14/202026-05-18 — 14/202026-05-28 — 12/202026-06-10 — 11/202026-06-12 — 11/202026-06-26 — 11/202026-06-28 — 11/202026-06-29 — 11/202026-07-03 — 11/202026-07-13 — 11/202026-07-19 — 11/20

Viability

13/20
2002026-04-20 — 13/202026-04-21 — 13/202026-04-30 — 13/202026-05-04 — 13/202026-05-05 — 13/202026-05-16 — 13/202026-05-18 — 13/202026-05-28 — 13/202026-06-10 — 13/202026-06-12 — 13/202026-06-26 — 13/202026-06-28 — 13/202026-06-29 — 13/202026-07-03 — 13/202026-07-13 — 13/202026-07-19 — 13/20

Interface

15/20
2002026-04-09 — 14/202026-04-10 — 14/202026-04-20 — 15/202026-04-21 — 15/202026-04-30 — 15/202026-05-04 — 15/202026-05-05 — 15/202026-05-16 — 15/202026-05-18 — 15/202026-05-28 — 15/202026-06-10 — 15/202026-06-12 — 15/202026-06-26 — 15/202026-06-28 — 15/202026-06-29 — 15/202026-07-03 — 15/202026-07-13 — 15/202026-07-19 — 15/20

Cap timeline

Q3 26severe-negative-sentimentsevere-negative-sentiment: 2026-05-28 → 2026-07-19

Notable events

  • 2026-04-20Jump+5 rating
  • 2026-05-28Cap +severe-negative-sentiment

What would move this next

Upgrade if: Zero-Trust Proxy KMS remediation ships and is independently verified, post-incident security audit published, community/enterprise sentiment recovers over 90+ days with no new incidents, independent F500 enterprise references confirmed, or self-hosted/data-residency option broadly available. Downgrade if: a new unpatched CVE or repeat breach surfaces, incident remediation stalls, community exodus toward Nango/Pipedream/native MCP servers materializes, funding concerns appear, or development velocity stalls (>90 days without changelog entry).