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