RepoRadar
Leave a Tip
Item detail
github.com

openai/openai-agents-js

openai/openai-agents-js is a framework in RepoRadar's Developer Tools section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Open on GitHub →Back to radar
Score8.8
Popularity71.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty7.0
Momentum8.0
Maturity8.3
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for JavaScript and TypeScript teams that want an official agent framework with tracing and guardrails instead of stitching together tool use, orchestration, and voice flows by hand.

Who should use it

JavaScript developers TypeScript developers voice-agent builders teams building agent products

Who should skip it

Pass on openai/openai-agents-js if its scope or audience does not match what your team is building right now.

About this signal

openai/openai-agents-js is tracked by RepoRadar as a framework in the Developer Tools section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, openai/openai-agents-js is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The openai/openai-agents-js record combines a 8.8/10 composite score with separate popularity (71.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

The SDK is designed to broker tool calls, MCP servers, and realtime/voice flows into external systems, so start with least-privilege credentials and explicit human approval on any side-effecting actions.

Evidence links
Closest alternatives / related signals
openai agent-sdk typescript voice-agents multi-agent
Verification record

What RepoRadar actually verified

Tested in a bounded workflow

Bounded representative workflow retained by RepoRadar verification harness. Last checked 2026-07-14T04:55:56.528112Z.

passed · cohort-20260713-openai-agents-js-deterministic-tool-workflow

Tester
RepoRadar automated local verification harness
Started
2026-07-14T04:55:43.977325Z
Completed
2026-07-14T04:55:56.528112Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded representative workflow
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 3 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Installed pinned OpenAI Agents JS and Zod packages with lifecycle scripts disabled and tracing disabled for the run.
  • Provided an in-memory Model that inspected the SDK-serialized tool definition and returned one deterministic function-call item.
  • Executed the SDK function tool against one allowlisted fixture path, stopped on its output, and retained request/call counts plus the final output.
  • Executed bounded check: Run an OpenAI Agents JS agent with an in-memory Model implementation that emits one function call, execute the allowlisted fixture-read tool, and stop on its output.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 12.55-second wall time.
Observed results
  • Command exited 0 after 12.55 seconds.
  • The Agents JS runner serialized the function tool, accepted the model's function-call item, invoked the tool exactly once, and promoted its marker output to the final result.
  • Expected marker 'CHECK_OK model_requests=1 tool_calls=1 final=REPORADAR_AGENTS_JS_FIXTURE_7319' was observed in retained output.
  • Validated result.json: 5 required marker(s) present and 0 excluded marker(s) absent; size and SHA-256 are retained.
Observed strengths
  • The Model interface and stop-on-first-tool behavior support a fully deterministic test of the real agent runner and tool execution path with tracing and network model calls absent.
Friction
  • A custom Model must emit the SDK's typed function-call item shape and usage object; provider-specific request/response behavior remains outside this local runner check.
  • Setup or runtime emitted 2 stderr line(s); the complete warnings/errors are preserved in the retained log.
Limitations
  • The custom deterministic Model proves the SDK runner and function-tool loop without a hosted model; it does not measure OpenAI model quality, provider transport, streaming, handoffs, guardrails, approval flows, or trace export.
  • This credential-free disposable workflow does not establish operator use, production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The pinned MIT SDK and in-memory model ran locally with no OpenAI API request, token charge, account, or hosted trace export.

Privacy assessment: Only a synthetic fixture was read by the allowlisted local tool; dependency installation contacted npm, while tracing was disabled and no content was sent to a provider.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

46 dated snapshots retained from 2026-06-19 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.8 current · +0.0 net
Repository momentum9.3 current · +1.3 net
GitHub stars (observed)3,580 current · +190 net
GitHub stars3,580 exact observation
Versionv0.15.0
Last release2026-08-11T05:38:48Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.89.33,580conditionaltry nowactive
2026-08-128.89.33,573conditionaltry nowactive
2026-08-118.89.33,565conditionaltry nowactive
2026-08-108.89.33,562conditionaltry nowactive
2026-08-098.89.33,557conditionaltry nowactive
2026-08-088.89.33,550conditionaltry nowactive
2026-08-078.89.33,519conditionaltry nowactive
2026-08-068.88.0Not recordedconditionaltry nownot recorded
2026-08-058.88.0Not recordedconditionaltry nownot recorded
2026-08-048.89.33,519conditionaltry nowactive
2026-08-038.89.33,519conditionaltry nowactive
2026-08-028.89.33,512conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 3573 → 3580.

stars changed

Stars changed: 3565 → 3573.

version changed

Version changed: v0.14.3 → v0.15.0.

stars changed

Stars changed: 3562 → 3565.

stars changed

Stars changed: 3557 → 3562.

stars changed

Stars changed: 3550 → 3557.

version changed

Version changed: v0.14.2 → v0.14.3.

stars changed

Stars changed: 3519 → 3550.

stars changed

Stars changed: 3512 → 3519.

stars changed

Stars changed: 3506 → 3512.

stars changed

Source-observed stars changed: 3503 → 3506. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed

Source-observed version changed: v0.14.1 → v0.14.2. Associated release timestamp: 2026-07-29T13:13:40Z → 2026-08-01T04:43:13Z. This reports the retained observation delta and does not infer why the upstream change occurred.