JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 27
  • Score
    100M100P100Q79965F
  • License Apache-2.0

DEPRECATED — install '@evalguard/sdk' instead. This package is a thin re-export shim kept so existing installs keep working; the canonical name is @evalguard/sdk.

Package Exports

  • evalguardai-sdk
  • evalguardai-sdk/index.cjs
  • evalguardai-sdk/package.json

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (evalguardai-sdk) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

evalguardai-sdk (deprecated)

⚠️ This package is deprecated. Install @evalguard/sdk instead.

npm install @evalguard/sdk

The evalguardai-sdk slot is kept so existing installs keep working — it re-exports everything from @evalguard/sdk and emits a one-time deprecation warning on first import.

Why the rename

The legacy name embedded the .ai TLD into the package handle. Industry convention (openai, @anthropic-ai/sdk, stripe, @vercel/*) keeps package names brand-only. Switching now — before customer integrations lock in the wrong name — avoids a future forced migration.

What you need to do

Replace:

import { EvalGuard } from "evalguardai-sdk";

with:

import { EvalGuard } from "@evalguard/sdk";

API surface is identical. No code changes needed beyond the import.

Verifying the canonical package

The canonical @evalguard/sdk is published with cryptographic provenance (npm OIDC trusted publisher + Sigstore). Verify after install:

npm install @evalguard/sdk
npm audit signatures

Reporting issues

Issues, PRs, and security reports go to the monorepo: https://github.com/EvalGuardAi/evalguard/issues