Automatic API Attack Tool vs GraphQL-Cop
Automatic API Attack Tool
github.comGraphQL-Cop
github.comSide by side
| Figure | Automatic API Attack Tool | GraphQL-Cop |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 0 |
| Spec score · API Security Testing Software | 8.2 (#7) | 7.2 (#23) |
| CI/CD | The project says it was built with CI/CD in mind and describes running it in a Jenkins job triggered by a schedule or code push. | The project describes itself as suitable for lightweight GraphQL CI/CD checks. |
| License | The repository lists an MIT license. | The repository identifies its license as MIT. |
| Purpose | The tool takes an API specification as input and generates and runs attacks based on it. | GraphQL-Cop is a lightweight Python utility for running common security tests against GraphQL APIs, including CI/CD checks. |
| Requirements | Running the tool requires Java 8 or higher and Gradle. | The listed requirements are Python 3 and the Requests library. |
| Support | The README directs users to source code documentation and gives an email address for questions; it directs bug reports to GitHub Issues. | The README provides command-line help and troubleshooting guidance for Docker file and dependency issues. |
Plans
In their own words
Automatic API Attack Tool
Automatic API Attack Tool is a free, MIT-licensed, self-hosted security tool for Windows and Linux. It takes a Swagger 2.0 API specification in JSON or YAML and generates and runs attacks from that definition. Fuzzing scenarios send generated values within the specification’s boundaries and values that violate them, including random invalid values for checked parameters. The project describes extensibility for attack types such as illegal resource access, XSS, SQL injection, and RFI, and supports authorization and input-validation testing. It reports request details, expected-response checks, and a summary. TestNG results are written under build/testng-results, while bad requests are saved in a bad_requests folder. Optional host and port arguments support routing through a proxy. The project is intended for CI/CD and describes scheduled or code-push Jenkins jobs. Running it requires Java 8 or higher and Gradle. Windows build instructions use gradlew.bat build; Linux instructions create an executable from a shell script and the JAR. API discovery is not included.
GraphQL-Cop
GraphQL-Cop has no write-up on Specifiction yet; its figures are above.