Alternatives to SourceHut
Other Developer collaboration and CI vendors we measure, sorted by how much they publish that SourceHut does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from SourceHut on at least one criterion we measured for both. Public transparency score, not a product or security rating.
SourceHut has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and SourceHut does not” is the one that closes them.
| Vendor | Score | Publishes, and SourceHut does not | SourceHut publishes, and they do not | |
|---|---|---|---|---|
| CircleCIcircleci.com | 74/100 | 8 Subprocessor list, Data location stated, Status page with history, +5 | 1 No third-party tracking before consent | Compare |
| CodeRabbitcoderabbit.ai | 70/100 | 8 Data processing agreement, Data location stated, Certifications named, +5 | 1 No third-party tracking before consent | Compare |
| Terramateterramate.io | 74/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 No third-party tracking before consent | Compare |
| GitHubgithub.com | 57/100 | 6 Subprocessor list, Status page with history, Certifications named, +3 | 1 No third-party tracking before consent | Compare |
| Replitreplit.com | 71/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 No third-party tracking before consent | Compare |
| Namespacenamespace.so | 52/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Codacycodacy.com | 39/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Codercoder.com | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 2 Public pricing, No third-party tracking before consent | Compare |
| Scalrscalr.com | 36/100 | 3 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Aviatoraviator.co | 35/100 | 3 Subprocessor list, Status page with history, Certifications named | 1 No third-party tracking before consent | Compare |
| Buddybuddy.works | 35/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Codeclimatecodeclimate.com | 35/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | 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.