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

[bot] Instrument Portkey AI (140,424 weekly downloads)

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
56/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
node.js, typescript
Domain
observability-sre

Research direction

Start by reading the existing openrouter and ai-sdk auto-instrumentation configs, the registry in js/src/auto-instrumentations/configs/all.ts, and the scenarios under e2e/scenarios/. Compare those patterns with the portkey-ai SDK sources and its Portkey client and chat completions APIs. Done means Portkey generation and streaming calls are instrumented and covered by an end-to-end scenario.

Written by the indexing model from the issue text.

Description

<!-- library-gap-audit: portkey-ai-gateway-sdk -->

Summary

Portkey AI's official Node.js SDK (portkey-ai) is a drop-in, OpenAI-SDK-shaped client (portkey.chat.completions.create(...)) that routes generation calls through Portkey's gateway to 250+ LLMs, with its own prompt-management and completion-execution surface distinct from the underlying provider SDKs. This execution surface is not instrumented anywhere in this repository.

What's missing

  • new Portkey({...}) client construction and portkey.chat.completions.create(...) (and streaming variants) — the SDK's primary generation-execution API — has no auto-instrumentation config, wrapper, or e2e scenario in this repo.
  • None of portkey-ai, Portkey, or PORTKEY_GATEWAY_URL appear anywhere in js/src/, js/src/auto-instrumentations/configs/all.ts, or any e2e/scenarios/* directory. (This is distinct from the already-instrumented openrouter/ai-sdk gateway-style configs, which target different packages.)

Weekly downloads

Weekly downloads: 140,424 (as of 2026-09-14; window 2026-09-05–2026-09-11; source https://api.npmjs.org/downloads/point/last-week/portkey-ai).

Braintrust docs status

unclear — Braintrust publishes a comparison article, "Braintrust vs Portkey" (https://www.braintrust.dev/articles/braintrust-vs-portkey), describing a pattern where Portkey stays in the request path for routing/guardrails while traces are sent to Braintrust "through its SDK or OpenTelemetry integration" — but this describes manual OTel/generic tracing, not a dedicated auto-instrumentation wrapper for the portkey-ai package. Portkey does not appear in Braintrust's main integrations catalog at https://www.braintrust.dev/docs/integrations (full grid enumerated in the companion E2B gap issue).

Upstream sources

Local repo files inspected

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

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.