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

[bot] RubyLLM moderation API (`RubyLLM.moderate`) not instrumented

Open
  • Is something wrong?
#176 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
ruby
Domain
observability

Research direction

Start with lib/braintrust/contrib/ruby_llm/patcher.rb and integration.rb, then compare the moderation pattern in lib/braintrust/contrib/openai/instrumentation/moderations.rb and openai/patcher.rb lines 131–170. Done means RubyLLM.moderate and its alias are instrumented with the stated input, metadata, moderation output, and latency, with the integration registered and loading detection updated.

Written by the indexing model from the issue text.

Description

Summary

RubyLLM.moderate is a model execution call that invokes OpenAI's moderation API to classify text for harmful content. It is not instrumented by the Braintrust Ruby SDK. The existing RubyLLM integration only patches RubyLLM::Chat.

This is distinct from issue #136 (RubyLLM embed, paint, and transcribe APIs not instrumented), which covers three other non-chat RubyLLM execution surfaces but explicitly omits moderation.

What is missing

RubyLLM.moderate("text") (aliased as RubyLLM::Moderation.moderate) makes a live API request to OpenAI's moderation endpoint using models such as omni-moderation-latest or text-moderation-007. It returns a RubyLLM::Moderation object with:

  • flagged — overall boolean
  • Per-category flags and confidence scores
  • id and model from the API response

This is the same class of execution call as the moderations already instrumented for the openai and ruby-openai integrations (ModerationsPatcher in both). A parallel RubyLLM::ModerationPatcher would follow the same pattern.

What a span should capture
  • Input: the text string being moderated
  • Metadata: model (e.g., omni-moderation-latest), provider (ruby_llm), endpoint
  • Output: flagged categories and scores (or summary)
  • Metrics: no token usage is returned by the moderation API, but latency should be captured

Braintrust docs status

not_found — The Braintrust RubyLLM integration docs at https://www.braintrust.dev/docs/integrations/sdk-integrations/ruby-llm cover chat completions and tool calls but do not mention moderation. The OpenAI provider docs at https://www.braintrust.dev/docs/providers/openai document moderation instrumentation via the openai gem but not via RubyLLM.

Upstream sources

Local files inspected

  • lib/braintrust/contrib/ruby_llm/patcher.rb — defines only ChatPatcher; no ModerationPatcher
  • lib/braintrust/contrib/ruby_llm/integration.rb — registers only [ChatPatcher]; loaded? checks defined?(::RubyLLM::Chat) only
  • lib/braintrust/contrib/openai/instrumentation/moderations.rb — demonstrates the existing moderation instrumentation pattern in this repo
  • lib/braintrust/contrib/openai/patcher.rb (lines 131–170) — ModerationsPatcher for reference
Dominant language
Ruby
Stars
9
Forks
10
Avg merge
22h 10m
Merged PRs (30d)
6

Getting set up

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-ruby

All issues in braintrustdata/braintrust-sdk-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.