Transparency alternatives to Patchstack
Other Vulnerability management vendors we measure, sorted by how much we found at them and not at Patchstack. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Patchstack on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Patchstack has 7 gaps in what we could measure: Data processing agreement, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Patchstack” is the one that closes them.
| Vendor | Score | Found there, not found at Patchstack | Found at Patchstack, not found there | |
|---|---|---|---|---|
| Invictiinvicti.comSee also Transparency alternatives to Invicti | 83/100 | 5 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Snyksnyk.ioSee also Transparency alternatives to Snyk | 74/100 | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | 1 Subprocessor list | Compare |
| Rapid7rapid7.comSee also Transparency alternatives to Rapid7 | 70/100 | 5 Data processing agreement, Status page with history, Uptime SLA with a figure, +2 | 2 Data location stated, Certifications named | Compare |
| Sucurisucuri.netSee also Transparency alternatives to Sucuri | 52/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Data location stated, Certifications named | Compare |
| Wizwiz.ioSee also Transparency alternatives to Wiz | 43/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Data location stated, Public pricing | Compare |
| Intruderintruder.ioSee also Transparency alternatives to Intruder | 57/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Subprocessor list, Named privacy contact | Compare |
| SonarSourcesonarsource.comSee also Transparency alternatives to SonarSource | 57/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| Probelyprobely.comSee also Transparency alternatives to Probely | 48/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Subprocessor list, Named privacy contact | Compare |
| Semgrepsemgrep.devSee also Transparency alternatives to Semgrep | 48/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Subprocessor list, Named privacy contact | Compare |
| Detectifydetectify.comSee also Transparency alternatives to Detectify | 43/100 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Subprocessor list, Data location stated | Compare |
| Veracodeveracode.comSee also Transparency alternatives to Veracode | 43/100 | 3 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| StackHawkstackhawk.comSee also Transparency alternatives to StackHawk | 39/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Subprocessor list, Data location stated | 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.