Infrastructure configuration signals
Terraform risk signals that fit into CI/CD.
Analyze Terraform source or terraform show -json output for actionable infrastructure configuration risks before an apply.
POST /v1/terraform-risk/analyze
curl -X POST https://api.antops.dev/v1/terraform-risk/analyze \
-H "X-API-Key: YOUR_RAPIDAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"analysis_type": "terraform",
"content": "resource \"aws_security_group\" \"web\" { ... }"
}'200 OK
{
"analysis_type": "terraform",
"score": 62,
"status": "fair",
"summary": { "high": 2 },
"issues": [{ "category": "network" }]
}Capabilities
One input. Useful signals.
Use cases
Designed for engineering workflows.
- Add an infrastructure risk gate before apply
- Surface review signals in pull requests
- Send Terraform plan findings to an engineering workflow
Integrate
Keep the workflow yours.
- Run terraform plan, then terraform show -json in GitHub Actions
- Send source or plan JSON with a REST call
- Fail a job on critical or high findings according to your policy
Scope and limitations
Signals, not unsupported promises.
- AntOps performs static analysis and never executes Terraform.
- It does not apply plans or access cloud credentials.
- Findings are technical signals and should be reviewed in the context of your environment.
FAQ
Before you call the API.
What Terraform input does the API accept?
Use analysis_type terraform for source text or plan_json for valid output from terraform show -json.
Can I use it in GitHub Actions?
Yes. The public examples repository includes a workflow that prepares a plan JSON, calls AntOps and evaluates the response.
Does it apply infrastructure changes?
No. It analyzes the submitted source or plan JSON only.
Ready to integrate