Transparency alternatives to YesWeHack
Other Vulnerability management vendors we measure, sorted by how much they publish that YesWeHack does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from YesWeHack on at least one criterion we measured for both. Public transparency score, not a product or security rating.
YesWeHack has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and YesWeHack does not” is the one that closes them.
| Vendor | Score | Publishes, and YesWeHack does not | YesWeHack publishes, and they do not | |
|---|---|---|---|---|
| Invictiinvicti.com | 83/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | nothing | Compare |
| Rapid7rapid7.com | 70/100 | 7 Data processing agreement, Subprocessor list, Status page with history, +4 | 1 security.txt (RFC 9116) | Compare |
| Intruderintruder.io | 57/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 1 security.txt (RFC 9116) | Compare |
| Snyksnyk.io | 57/100 | 5 Data processing agreement, Status page with history, Certifications named, +2 | nothing | Compare |
| Holm Securityholmsecurity.com | 52/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| Sucurisucuri.net | 52/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | 1 security.txt (RFC 9116) | Compare |
| Patchstackpatchstack.com | 43/100 | 5 Subprocessor list, Data location stated, Public pricing, +2 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Arnicaarnica.io | 48/100 | 4 Subprocessor list, Data location stated, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Semgrepsemgrep.dev | 48/100 | 4 Data location stated, Status page with history, Public pricing, +1 | nothing | Compare |
| SonarSourcesonarsource.com | 48/100 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Detectifydetectify.com | 43/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | nothing | Compare |
| Veracodeveracode.com | 43/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.