Skip to main content

NVIDIA NeMo Evaluator

The goal of NVIDIA NeMo Evaluator is to advance and refine state-of-the-art methodologies for model evaluation, and deliver them as modular evaluation packages (evaluation containers and pip wheels) that teams can use as standardized building blocks.

Quick start guide

NVIDIA NeMo Evaluator provide you with evaluation clients, that are specifically built to evaluate model endpoints using our Standard API.

Launching an evaluation for an LLM

  1. Install the package

    pip install nvidia-eval-factory-garak
    
  2. (Optional) Set a token to your API endpoint if it's protected

    export MY_API_KEY="your_api_key_here"
    
  3. List the available evaluations:

    $ nemo-evaluator ls
    Available tasks:
    * garak (in garak)
    ...
    
  4. Run the evaluation:

    nemo-evaluator run_eval \
        --eval_type garak \
        --model_id microsoft/phi-4-mini-instruct \
        --model_url https://integrate.api.nvidia.com/v1/chat/completions \
        --model_type chat \
        --api_key_name MY_API_KEY \
        --output_dir /workspace/results
    
  5. Gather the results

    cat /workspace/results/results.yml
    

Command-Line Tool

Each package comes pre-installed with a set of command-line tools, designed to simplify the execution of evaluation tasks. Below are the available commands and their usage for the garak:

Commands

1. List Evaluation Types

nemo-evaluator ls

Displays the evaluation types available within the harness.

2. Run an evaluation

The nemo-evaluator run_eval command executes the evaluation process. Below are the flags and their descriptions:

Required flags

  • --eval_type <string> The type of evaluation to perform
  • --model_id <string> The name or identifier of the model to evaluate.
  • --model_url <url> The API endpoint where the model is accessible.
  • --model_type <string> The type of the model to evaluate, currently either "chat" or "completions".
  • --output_dir <directory> The directory to use as the working directory for the evaluation. The results, including the results.yml output file, will be saved here. Make sure to use the absolute path.

Optional flags

  • --api_key_name <string> The name of the environment variable that stores the Bearer token for the API, if authentication is required.
  • --run_config <path> Specifies the path to a YAML file containing the evaluation definition.

Example

nemo-evaluator run_eval \
    --eval_type garak \
    --model_id my_model \
    --model_type chat \
    --model_url http://localhost:8000/v1/chat/completions \
    --output_dir /workspace/evaluation_results

If the model API requires authentication, set the API key in an environment variable and reference it using the --api_key_name flag:

export MY_API_KEY="your_api_key_here"

nemo-evaluator run_eval \
    --eval_type garak \
    --model_id my_model \
    --model_type chat \
    --model_url http://localhost:8000/v1/chat/completions \
    --api_key_name MY_API_KEY \
    --output_dir /workspace/evaluation_results

Configuring evaluations via YAML

Evaluations in NVIDIA NeMo Evaluator are configured using YAML files that define the parameters and settings required for the evaluation process. These configuration files follow a standard API which ensures consistency across evaluations.

Example of a YAML config:

config:
  type: garak
  params:
    parallelism: 50
    limit_samples: 20
    extra:
      probes: atkgen.Tox
target:
  api_endpoint:
    model_id: microsoft/phi-4-mini-instruct
    type: chat
    url: https://integrate.api.nvidia.com/v1/chat/completions
    api_key_name: NVIDIA_API_KEY

The priority of overrides is as follows:

  1. command line arguments
  2. user config (as seen above)
  3. task defaults (defined per task type)
  4. framework defaults

--dry_run option allows you to print the final run configuration and command without executing the evaluation.

Example:

nemo-evaluator run_eval \
    --eval_type garak \
    --model_id my_model \
    --model_type chat \
    --model_url http://localhost:8000/v1/chat/completions \
    --output_dir /workspace/evaluation_results \
    --dry_run

Output:

Rendered config:

command: "cat > garak_config.yaml << 'EOF'\nplugins:\n  {% if config.params.extra.probes\
  \ is not none %}probe_spec: {{config.params.extra.probes}}{% endif %}\n  extended_detectors:\
  \ true\n  model_type: {% if target.api_endpoint.type == \"completions\" %}nim.NVOpenAICompletion{%\
  \ elif target.api_endpoint.type == \"chat\" %}nim.NVOpenAIChat{% endif %}\n  model_name:\
  \ {{target.api_endpoint.model_id}}\n  generators:\n    nim:\n      uri: {{target.api_endpoint.url\
  \ | replace('/chat/completions', '') | replace('/completions', '')}}\n      {% if\
  \ config.params.temperature is not none %}temperature: {{config.params.temperature}}{%\
  \ endif %}\n      {% if config.params.top_p is not none %}top_p: {{config.params.top_p}}{%\
  \ endif %}\n      {% if config.params.max_new_tokens is not none %}max_tokens: {{config.params.max_new_tokens}}{%\
  \ endif %}\nsystem:\n  parallel_attempts: {{config.params.parallelism}}\n  lite:\
  \ false\nEOF\n{% if target.api_endpoint.api_key_name is not none %}\nexport NIM_API_KEY=${{target.api_endpoint.api_key_name}}\
  \ &&\n{% else %}\nexport NIM_API_KEY=dummy &&\n{% endif %}\nexport XDG_DATA_HOME={{config.output_dir}}\
  \ &&\ngarak --config garak_config.yaml --report_prefix=results\n"
framework_name: garak
pkg_name: garak
config:
  output_dir: /workspace/evaluation_results
  params:
    limit_samples: null
    max_new_tokens: 150
    max_retries: null
    parallelism: 32
    task: garak
    temperature: 0.1
    request_timeout: null
    top_p: 0.7
    extra:
      probes: null
  supported_endpoint_types:
  - chat
  - completions
  type: garak
target:
  api_endpoint:
    api_key_name: null
    model_id: my_model
    stream: null
    type: chat
    url: http://localhost:8000/v1/chat/completions


Rendered command:

cat > garak_config.yaml << 'EOF'
plugins:
  
  extended_detectors: true
  model_type: nim.NVOpenAIChat
  model_name: my_model
  generators:
    nim:
      uri: http://localhost:8000/v1
      temperature: 0.1
      top_p: 0.7
      max_tokens: 150
system:
  parallel_attempts: 32
  lite: false
EOF

export NIM_API_KEY=dummy &&

export XDG_DATA_HOME=/workspace/evaluation_results &&
garak --config garak_config.yaml --report_prefix=results

FAQ

Deploying a model as an endpoint

NVIDIA NeMo Evaluator utilize a client-server communication architecture to interact with the model. As a prerequisite, the model must be deployed as an endpoint with a NIM-compatible API.

Users have the flexibility to deploy their model using their own infrastructure and tooling.

Servers with APIs that conform to the OpenAI/NIM API standard are expected to work seamlessly out of the box.

Release files for nvidia-eval-factory-garak 26.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for nvidia-eval-factory-garak 26.3
File Interpreter ABI Platform
nvidia_eval_factory_garak-26.3-py3-none-any.whl Python 3 none any Details

Release files / nvidia_eval_factory_garak-26.3-py3-none-any.whl

Download URL nvidia_eval_factory_garak-26.3-py3-none-any.whl
Size 15.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
40313f77ade73810306e009a95307bda7ef875b5c73d2f2ac0edd854c909001b
BLAKE2b-256 checksum
How to use checksums
c2eccaf841bf9ece7d046432fa88fd680d0ce1ba8238e93b183d047db1e66a5f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

Security for nvidia-eval-factory-garak 26.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page