Application Security
Application security tools find and block weaknesses in software you build or run.
27 results in Application Security
Active Pro listings from this category appear first. Your sort applies within Pro and Free results.
Shortlists for Application Security
Explore collections with tools relevant to this category, grouped by deployment, source model or workload.
Open-source IAM tools for developers and platform teams →
3 matching tools from this category
IT tools with an API →
16 matching tools from this category
Self-hosted IT tools →
15 matching tools from this category
How to choose Application Security tools
Application security tools find and block weaknesses in software you build or run. Static analysis reads source code, dynamic testing probes a running application from outside, software composition analysis flags vulnerable open-source dependencies, and runtime protection watches production traffic for attacks. The category also includes reverse engineering frameworks and binary analysis kits used to study compiled programs, which separates it from network security and infrastructure vulnerability scanning.
Who uses these tools
- Application security engineers running testing programmes
- Developers fixing findings inside their pull requests
- Security researchers analysing compiled binaries
Capabilities to compare
- Static and dynamic application testing
- Dependency and container image scanning
- Runtime attack detection and blocking
- Developer tooling integration in editors and pipelines
- Disassembly, decompilation and binary analysis
Operating considerations
- False positive rates that drain developer attention
- Source code uploaded to a vendor's cloud
- Pricing by developer, application or scan volume
- Coverage of the languages and frameworks you use
Selection checklist
- Scan one representative repository and triage the results to measure real versus false findings.
- Confirm the tool supports every language, framework and package manager in your stack.
- Check that findings appear where developers work, such as pull requests, rather than only in a portal.
- Decide which tests run on every commit and which run on a schedule against staging.
What belongs in this category: A product belongs here when it tests, analyses or protects application code, dependencies or binaries, rather than scanning networks and hosts or managing identities and endpoints.
Typical use cases
- Blocking pull requests that introduce vulnerable dependencies
- Scanning a public web application for exploitable flaws
- Analysing a suspicious binary or firmware image
- Protecting a legacy application at runtime while fixes are planned
Trade-offs to model
- Open-source scanners cost nothing to adopt but need tuning, while commercial platforms bundle triage, reporting and support.
- Shift-left testing catches issues early in code, whereas runtime protection covers what reaches production but adds an agent.
Common mistakes
- Turning on every rule at once and burying developers in findings they learn to ignore.
- Scanning only first-party code and missing vulnerabilities in transitive open-source dependencies.
Application Security on iThub in figures
iThub lists 27 tools in Application Security. 18 of 27 are open source, 15 of 27 can be self-hosted, 25 of 27 have a free, freemium or open-source pricing model and 16 of 27 offer an API.
- Tools listed
- 27
- Open source
- 18
- Self-hostable
- 15
- Free to start
- 25
- With an API
- 16
- Web app
- 12
- Desktop app
- 14
Recently added: OpenCodeReview, Web-Check, SafeLine, TruffleHog
Explore vulnerability management tools Browse open-source security tools Choose reverse engineering targets and check evidence
Continue the technical evaluation
Use the resources that match your decision stage. Profile data and linked sources were refreshed through November 15, 2026.
