Documentation

Evaluators

Evaluators are Privateer plugins — signed binaries that turn Gemara artifacts into automated checks against live systems, and emit machine-readable evidence.

Privateer is a separate OSS project: a CLI that, in its own words, lets you streamline your security and compliance validation by treating compliance as a data engineering problem. It runs plugins — community-maintained validators — against your infrastructure and produces structured evidence of compliance.

What an evaluator does

An evaluator plugin executes validation tests against resources and emits machine-readable evidence, operating at what Gemara calls the Evaluation layer (Layer 5). Because plugins can be auto-generated from Gemara Control Catalogs, a control document can become a runnable check — closing the loop from "what should be true" to "is it true right now."

The registry hosts these as signed, multi-platform binaries. Each evaluator page shows its platforms and whether the publish signature was verified — browse them under Evaluators.

The pvtr CLI

Privateer's command-line tool is pvtr. Its main operations:

  • install — add a plugin from the registry to your environment.
  • run — execute one or more plugins against live infrastructure in a single pass.
  • publish — sign and publish a plugin to the registry.

Publishing an evaluator requires ownership of the target namespace, and the hub verifies the plugin's signature at ingest — see Publishing and Verifying & trust.

📖 Privateer is its own project — for installing, writing, and running plugins, the authoritative docs are at privateerproj.com. This page covers only how evaluators relate to grc.store.