Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[bot] Instrument Composio (631,324 weekly downloads)

Open
  • Is something wrong?
#2,481 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
observability

Research direction

Start with js/src/auto-instrumentations/configs/all.ts and inspect the existing e2e/scenarios/ directory to understand how integrations are registered and tested. Add coverage for @composio/core, including its tool-execution surface and toolset adapters, with an auto-instrumentation config, wrapper, and e2e scenario. Done means the integration appears in the registry and the scenario verifies instrumentation.

Written by the indexing model from the issue text.

Description

<!-- library-gap-audit: composio-core-typescript-sdk -->

Summary

Composio is an official platform SDK that equips AI agents with tool execution across 1,000+ third-party toolkits (GitHub, Slack, Notion, etc.), including agent-framework-specific tool-set adapters (OpenAIToolSet, and adapters for LangChain, CrewAI, Autogen, and others). Its current TypeScript SDK, @composio/core (successor to the now-legacy composio-core package), exposes a meaningful tool-calling execution surface — connecting, authenticating, and invoking tools on behalf of an agent — that is not instrumented anywhere in this repository.

What's missing

  • @composio/core's tool-execution surface (e.g. composio.tools.execute(...), toolset adapters like OpenAIToolSet used inside an agent's tool-calling loop) has no auto-instrumentation config, no wrapper, and no e2e scenario in this repo.
  • None of composio, Composio, or composio-core appear anywhere in js/src/, js/src/auto-instrumentations/configs/all.ts, or any e2e/scenarios/* directory.

Weekly downloads

Weekly downloads: 631,324 (as of 2026-09-14; window 2026-09-05–2026-09-11; source https://api.npmjs.org/downloads/point/last-week/@composio%2Fcore). Note: the older, now-legacy composio-core package trails far behind at 12,551/week over the same window (https://api.npmjs.org/downloads/point/last-week/composio-core) — @composio/core is the actively maintained current SDK per Composio's own migration guide (https://v3.docs.composio.dev/docs/migration).

Braintrust docs status

not_found — Composio does not appear in Braintrust's integrations catalog. Checked https://www.braintrust.dev/docs/integrations (full enumerated integration grid — see list in the companion E2B gap issue for the complete enumeration) and the Braintrust MCP page (https://www.braintrust.dev/docs/integrations/developer-tools/mcp). Composio is absent from both.

Upstream sources

Local repo files inspected

  • js/src/auto-instrumentations/configs/all.ts (full instrumentation registry — no Composio entry)
  • Repo-wide case-insensitive search for composio across the working tree (no matches)
  • e2e/scenarios/ directory listing (no composio-named scenario)
Dominant language
TypeScript
Stars
28
Forks
15
Avg merge
1d 22h
Merged PRs (30d)
73

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from braintrustdata/braintrust-sdk-javascript

All issues in braintrustdata/braintrust-sdk-javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.