head to head · open source
PayloadsAllTheThings vs inql
PayloadsAllTheThings has 82,599 GitHub stars, 17,572 forks, 36 open issues and last shipped 13 days ago. inql has 1,814 stars, 190 forks, 29 open issues and last shipped 2 days ago. PayloadsAllTheThings leads on adoption by 4,453% (82,599 vs 1,814 stars). PayloadsAllTheThings is written in Python under MIT; inql is written in Kotlin under Apache-2.0. PayloadsAllTheThings has attracted 21% as many forks as stars, inql 10%. inql was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (bugbounty, penetration-testing), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| PayloadsAllTheThings | inql | |
|---|---|---|
| GitHub stars | ★ 83K | ★ 1.8K |
| License | MIT | Apache-2.0 |
| Written in | Python | Kotlin |
| Last push | 2026-10-30 | 2026-11-10 |
| Forks | ⑂ 18K | ⑂ 190 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick PayloadsAllTheThings if
- You weight community size — 83K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick inql if
- You want the inql feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Kotlin
- You evaluated both and inql fits your workflow better
About PayloadsAllTheThings
Payloads All The Things A list of useful payloads and bypasses for Web Application Security. Feel free to improve with your payloads and techniques! You can also contribute with a :beers: IRL, or using the sponsor button. An alternative display version is available at PayloadsAllTheThingsWeb. :book: Documentation Every section contains the following files, you can use the template vuln folder to create a new chapter: README.md vulnerability description and how to exploit it, including several payloads Intruder a set of files to give to Burp Intruder Images pictures for the README.md Files some files referenced…
read the full PayloadsAllTheThings overview →
About inql
InQL v6.1.2 Burp Extension for Advanced GraphQL Testing :rocket: Introduction Welcome to InQL, an open source GraphQL testing tool. This tool provides features designed to enhance your GraphQL testing experience, making it more efficient and effective. We appreciate your trust in InQL. Happy testing! :star2: Key Features The InQL user interface is equipped with three primary components: the Scanner , the Batch Queries , and the Engine Fingerprinting tab :mag right: Scanner The Scanner is the core of InQL, where you can analyze a GraphQL endpoint or a local introspection schema file. It auto generates all…
More in Security & Privacy
Related comparisons
More Threat Detection & Response projects
Compare either of these against the rest of the Threat Detection & Response field.
Frequently asked questions
Is PayloadsAllTheThings or inql more popular?
PayloadsAllTheThings has 82,599 GitHub stars and inql has 1,814. PayloadsAllTheThings has the larger community by that measure.
Are PayloadsAllTheThings and inql free?
Both are open source. PayloadsAllTheThings is licensed under MIT and inql under Apache-2.0. Neither carries a licence fee.
What is the difference between PayloadsAllTheThings and inql?
PayloadsAllTheThings is written in Python and inql in Kotlin. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, PayloadsAllTheThings or inql?
Choose PayloadsAllTheThings if you want the larger community (82,599 stars) or its MIT licence terms. Choose inql if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.