/ guides / Configuring requirements

This guide walks through writing the [policy] block of an openvet.toml. For the full field-by-field reference, see Requirement syntax.

TODO: write me. Suggested examples to cover:

  • “all production deps must have a safe-to-deploy claim from someone I trust”
  • “all crypto-related deps must have a crypto-reviewed claim”
  • “all transitive deps must satisfy non-malicious
  • exemptions for legacy packages
  • per-criterion delegation (whose audits count for what)