Trivy

Connect an agent via an official MCP server G

Agent access

Drive the product through a documented public API G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Plug MCP servers into this product so it can use their tools G

Agent access

Run the product headlessly / in CI for automation G

Agent access

Use an official CLI G

Agent access

Operate the product with natural-language commands G

Agentic features

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Set up automations that run autonomously in the background G

Agentic features

Build against official SDKs G

Agent access

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Explore an interactive API reference with runnable examples G

Api quality

Point an agent at llms.txt or agent-oriented docs G

Agent access

Rely on versioned APIs with a documented deprecation policy G

Api quality

Subscribe to events via webhooks G

Agent access

Issue scoped/least-privilege API credentials for an agent G

Agent access

Test against a sandbox environment without touching production data G

Api quality

Scan container images for OS-package and application-layer vulnerabilities before deploying them C

Containers

Scan my dependency manifests and lockfiles for packages with known vulnerabilities C

Sca scanning

Have an agent run a scan headlessly via the CLI, parse machine-readable results, and file issues for real findings G

Agent scanning

Self-host the core product G

Export all of my data in open formats and leave G

Scan a repository and its full git history for hardcoded secrets and credentials C

Secret scanning

Run scans in CI on every pull request and fail the build on new findings via exit codes C

Ci gates

Use AI to triage findings — explaining them, deduplicating, and flagging likely false positives C

Ai triage

Run static analysis that finds vulnerability classes like injection and XSS in my source code C

Code analysis

Baseline or ignore existing and false-positive findings so only new issues alert C

Fp management

Define rules that trigger actions automatically on events G

Prevent my data from being used to train AI models G

Run the scanner as a pre-commit hook so secrets and issues never enter my git history C

Pre commit

Generate a software bill of materials (SPDX or CycloneDX) for my project or image C

Sbom

Scan Terraform, Kubernetes, and other IaC files for security misconfigurations C

Iac misconfig

Scan projects across all the major languages and package ecosystems my organization uses C

Coverage

Read the product's source under an open license G

Wire the scanner into my coding agent so AI-generated code is scanned for issues before it lands C

Agent scanning

Perform bulk operations across many items at once G

Scan non-git sources like S3 buckets, Docker images, and CI logs for leaked secrets C

Secret scanning

Apply suggested or automatic code fixes for findings instead of only reading reports C

Fix suggestions

Define custom detection rules for my organization's internal token and secret formats C

Custom detection

Do everything through the API that I can do in the UI G

Emit scan results in machine-readable formats like JSON or SARIF for downstream tooling C

Output formats

Get concrete upgrade paths or automated fix pull requests that remediate vulnerable dependencies C

Dependency fixes

Have AI draft remediation pull requests for security findings that I review and merge C

Ai remediation

Have detected secrets verified against the issuing service so I know which ones are live C

Secret scanning

Choose where my data is stored (region/residency) G

Control data retention and deletion G

Detect taint-style vulnerabilities that flow across files and function boundaries C

Code analysis

Filter and gate on findings by severity or confidence so low-value noise does not block builds C

Fp management

Opt out of telemetry and usage tracking G

Prioritize dependency alerts by whether the vulnerable code is actually reachable from my code C

Sca scanning

Schedule recurring jobs or workflows G

See scan findings surfaced as pull-request comments or checks in GitHub or GitLab C

Ci gates

Write custom static-analysis rules in a simple syntax and share them across repositories C

Custom rules

Detect the licenses of my dependencies and enforce a license policy in scans C

Licenses

Version, review, and roll back my automations G