[bot] Instrument Deepgram (991,641 weekly downloads)

Aberta
  • Algo errado?
#2,294 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
node.js, typescript
Domínio
developer-experience, observability-sre

Direção de pesquisa

Comece lendo os wrappers existentes em js/src/wrappers/, os plugins de instrumentação em js/src/instrumentation/plugins/, as configurações de auto-instrumentação em js/src/auto-instrumentations/configs/ e os cenários e2e em e2e/scenarios/. Use as superfícies de execução do @deepgram/sdk listadas como escopo de cobertura; considera-se concluído quando a instrumentação do Deepgram existe nas camadas relevantes e um cenário e2e a valida.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

<!-- library-gap-audit: deepgram-node-sdk -->

Summary

Deepgram publishes an official Node/TypeScript SDK, @deepgram/sdk on npm, providing execution APIs for prerecorded and live/streaming speech-to-text transcription, and text-to-speech generation. This repository has zero instrumentation for any Deepgram SDK surface — no wrapper, no diagnostics channel, no plugin, no auto-instrumentation config, no e2e scenario.

What's missing

Execution surfaces exposed by @deepgram/sdk that are not instrumented:

SDK Method Description
client.listen.v1.media.transcribeFile({ model, ... }) Prerecorded audio transcription
client.listen.v1.connect({ model, language, ... }) Live/streaming transcription over a WebSocket-style connection
client.speak.v1.audio.generate({ text, model, ... }) Text-to-speech generation
client.agent.v1.connect(...) / connection.sendAgentV1Settings(...) Conversational voice agent execution
client.read.v1.text.analyze(...) Text intelligence (sentiment/topic/intent) execution

None of these are covered by existing provider instrumentation — the SDK has its own fetch/WebSocket-based client and does not depend on openai or any already-instrumented package.

No coverage in any instrumentation layer:

  • No wrapper function (e.g. wrapDeepgram()) in js/src/wrappers/
  • No channel definitions or plugin in js/src/instrumentation/plugins/
  • No auto-instrumentation config in js/src/auto-instrumentations/configs/
  • No e2e test scenario under e2e/scenarios/
  • Repo-wide grep for deepgram (case-insensitive) returns zero matches anywhere in the repo

Weekly downloads

Weekly downloads: 991,641 (as of 2026-10-14; window 2026-10-06 to 2026-10-12; source https://api.npmjs.org/downloads/point/last-week/@deepgram/sdk)

Braintrust docs status

not_found. Deepgram does not appear anywhere on the Braintrust integrations index page — https://www.braintrust.dev/docs/integrations — which lists AI-provider and framework integrations but has no entry for Deepgram or any speech-to-text/voice provider. The page's only guidance for unlisted providers is the generic AI Proxy gateway (/docs/deploy/ai-proxy) or contacting Braintrust to request an integration.

Upstream references

Braintrust docs sources checked

Local files inspected

  • Repo-wide grep for deepgram|assemblyai|elevenlabs|11labs (case-insensitive) — zero matches
  • js/src/wrappers/ — full directory listing (37 files) — no deepgram.ts wrapper
  • js/src/instrumentation/plugins/ — no Deepgram channels or plugin file
  • js/src/auto-instrumentations/configs/ — full directory listing (28 files) — no Deepgram config entry
  • e2e/scenarios/ — no Deepgram test scenario
Linguagem predominante
TypeScript
Estrelas
29
Forks
22
Merge médio
1d 25min
PRs com merge (30d)
80

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de braintrustdata/braintrust-sdk-javascript

Todas as issues de braintrustdata/braintrust-sdk-javascript

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.