.dino.yml
Dino is configured through a.dino.yml file in your project root. Run dino init to generate one interactively, or create it manually.
For REST (OpenAPI) APIs, discovery and routing live in a tenant file under tenants/<id>.yml. Point the CLI at that tenant with tenant: in .dino.yml or dino scan --tenant <id>.
Minimal config (GraphQL, ad-hoc)
Minimal pointer (REST, tenant mode)
tenants/my-api.yml (see below), then:
Full reference (.dino.yml)
REST APIs — tenants/<id>.yml
Define each API under apis[]. The discovery plugin routes on type (graphql vs rest) and source (introspection vs openapi).
apis[] fields
JSON Schema
The# yaml-language-server comment at the top of your config file enables IDE autocomplete if you use the YAML extension in VS Code.
dino init adds this comment automatically.
Config file search order
Dino uses cosmiconfig to find your config. It searches in this order:.dino.ymlor.dino.yaml.dinorc(JSON or YAML).dinorc.json,.dinorc.yaml,.dinorc.ymlpackage.json→"dino"key
Precedence
When the same setting is defined in multiple places:--format markdown overrides format: json in your config file.
Smart defaults
If you omit fields, Dino applies sensible defaults:- All shipped pipeline modules enabled (RBAC matrix auto-skips when auth is not configured;
rest-fuzzerruns when REST operations are discovered) - Pipeline timeout: 300 seconds
- Per-request timeout: 30 seconds
- Snapshot dir:
.dino/snapshots - Watch interval: 60 seconds
- Watch autonomy:
observe(safe default — never blocks CI unless you opt in)
Examples
Ad-hoc scan (GraphQL, no tenant)
Authenticated scan with RBAC testing
REST scan (tenant)
tenants/acme-rest.yml defines apis[].type: rest and specPath. Then:
CI/CD with enforce mode
See the Installation guide for setting
DINO_AI_KEY and DINO_API_TOKEN without putting secrets in your config file.