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

Keep Jev answer confidence for OpenRouter evaluation models in Vercel AI

Open Beginner friendly
#24,860 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
observability

Research direction

Start in packages/server-utils/src/integrations/vercel-ai/vercel-ai-dc-subscriber.ts and inspect withProviderConfidence alongside the providerMetadata shapes described in the issue. Verify that OpenRouter evaluation answers preserve confidence and legend in gen_ai.output.messages, matching the existing typesafe-ai behavior.

Written by the indexing model from the issue text.

Description

Vercel AI experimental_evaluate with openrouter.evaluationModel('typesafe/jev-1.13') (@openrouter/ai-sdk-provider 3.1.0) gives an evaluate span, but the answers in gen_ai.output.messages lose confidence and legend.

The OpenRouter provider moves these fields into providerMetadata.openrouter.answers[<question id>] ({ confidence, legend }). Our withProviderConfidence in packages/server-utils/src/integrations/vercel-ai/vercel-ai-dc-subscriber.ts only reads providerMetadata.typesafe.confidence, which is the shape of @ai-sdk/typesafe-ai.

Expected

Evaluate answers from the OpenRouter provider keep confidence (choice, score) and legend (score), the same as answers from @ai-sdk/typesafe-ai.

Notes

  • OpenRouter also sends providerMetadata.openrouter.usage.cost and provider. We could record these too, but they are optional.
  • Related: Vercel AI experimental_evaluate (getsentry/sentry-javascript#24694).
Dominant language
TypeScript
Stars
8.8k
Forks
1.9k
Avg merge
1d 10h
Merged PRs (30d)
588

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 getsentry/sentry-javascript

All issues in getsentry/sentry-javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.