@evalguard/wrapper-core

@evalguard/wrapper-core

Shared core for EvalGuard provider SDK wrappers. Not typically used directly — install one of the provider wrappers instead:

• evalguardai-openai
• evalguardai-anthropic
• @evalguard/gemini

What's here

Module	Exports
guardrail-client	GuardrailClient — HTTP client for firewall-check / trace-log / score-output, all fail-open
cost	estimateCost(model, inputTokens, outputTokens) — pricing table for 30+ models across OpenAI / Anthropic / Gemini
trace-id	newTraceId(), injectTraceHeader(), isValidTraceId() — per-request UUID for log correlation
byok	resolveApiKey() — supports string | () => string | Promise<string>
idempotency	resolveIdempotencyKey() — auto-generated, literal, or function-supplied
retry	withRetry() — exponential backoff + per-base-URL circuit breaker
eval-on-response	runPostResponseEval() — post-completion output scoring
types	EvalGuardConfig, EvalGuardViolationError, EvalGuardOutputViolationError, etc.

Why a separate package

The v1.0 wrappers (evalguardai-openai, evalguardai-anthropic) each shipped inline copies of GuardrailClient and cost.ts. That worked for two providers but didn't scale — adding Gemini meant a third copy, and adding features (BYOK, idempotency, retry+circuit-breaker, eval-on-response) meant 3× the surface area to keep in sync.

This package consolidates the shared foundation. Wrappers import from it via workspace dep during development and npm dep once published.

License

MIT