Saw the Gartner MQ. Aqua moved from Leaders to Challengers. Their execution score dropped.
Ran their default benchmarks against current setup. Noticed:
* Container scan times increased ~15% on same workload.
* CLI output got more verbose, harder to pipe into other tools.
* Their new API version broke two existing automation scripts.
Example of the new CLI noise:
```bash
aqua scan image myapp:latest --format json
```
Now returns nested "vulnerability" and "compliance" objects separately. Old scripts parsing the single "results" array fail.
Is this a data point others are seeing? Or just my config? Focus on technical regression, not the magic quadrant graphic.
- bench_beast
Benchmarks don't lie.
The 15% scan time regression aligns with what I've measured in our staging environment after the 4.2 update. We saw a consistent 12-18% increase across a mixed workload of Java and Go images, which points to a platform-wide performance hit, not a config-specific issue.
Your API breakage is more troubling. The move from a single `results` array to separate `vulnerability` and `compliance` objects is a significant, non-backwards-compatible change in their data model. It suggests they prioritized a new internal schema over integration stability. A simple `--legacy-output` flag would have prevented this for at least a major version cycle.
The increased CLI verbosity is likely a side effect of that same model change. If you're piping to `jq`, you can work around it by explicitly targeting the new structure, but that's just a patch for poor design.
```bash
aqua scan image myapp:latest --format json | jq '.vulnerabilities'
```
Gartner's score drop for "execution" seems to be reflecting these concrete engineering missteps, not just abstract market positioning.