Static Docker configuration analysis
Static Docker security checks before you ship.
Analyze Dockerfile and Docker Compose text for configuration risk signals without building images or starting containers.
POST /v1/docker-scanner/scan
curl -X POST https://api.antops.dev/v1/docker-scanner/scan \
-H "X-API-Key: YOUR_RAPIDAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"scan_type": "dockerfile",
"content": "FROM python:3.12-slim\nUSER root"
}'200 OK
{
"scan_type": "dockerfile",
"score": 78,
"status": "good",
"summary": { "issue_count": 2 },
"issues": []
}Capabilities
One input. Useful signals.
Use cases
Designed for engineering workflows.
- Add a pre-merge Dockerfile policy signal
- Review Compose files submitted to a platform
- Provide container configuration feedback in an internal developer portal
Integrate
Keep the workflow yours.
- Read Dockerfile content in CI and send it as JSON
- Analyze a Compose artifact before deployment approval
- Fail or warn based on the returned severity summary
Scope and limitations
Signals, not unsupported promises.
- AntOps does not execute submitted Dockerfile or Compose content.
- It does not build images, pull registries or start containers.
- Static findings should complement your existing runtime and image-security controls.
FAQ
Before you call the API.
Does AntOps run my Dockerfile?
No. It performs static analysis on submitted text only; it does not build or execute images.
Does it support Docker Compose?
Yes. Set scan_type to compose and submit Docker Compose YAML.
Can it replace image scanning?
No. It identifies configuration risk signals and is best used alongside image, dependency and runtime controls.
Ready to integrate