
umami
Plausible.io
Fathom Analytics
Matomo
Google Analytics
Simple Analytics
Pirsch Analytics
Mixpanel
CodeClimate
Codacy
SonarQube
ESLint
CodeFactor.io
Coveralls
SensioLabs Insight
Source-Navigator NG
umami
CodeClimateBased on our record, umami should be more popular than CodeClimate. It has been mentiond 97 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I self-host Umami for my SaaS, ParserBee. The main reason I picked it: privacy-friendly, cookie-less, first-party analytics that adblockers supposedly leave alone because the script comes from your own domain. - Source: dev.to / 17 days ago
Umami told me Clew Directive got 14 visits last month. AWS told me I owed $31 for it. That works out to $2.21 a visitor, which would make it the most expensive free learning-path tool in California. - Source: dev.to / about 1 month ago
Also a small tooling aside โ if you're tracking how often skills get used across your team (or just want analytics on your dev blog without the GDPR cookie banner dance), privacy-focused options like Umami or Plausible give you full data ownership and a much lighter footprint than Google Analytics. I migrated two side projects to Umami last year and haven't looked back. - Source: dev.to / 3 months ago
Augur targets EU-regulated buyers. Putting Google Analytics on its landing page would be a self-own. I run Umami inside Augur's stack โ same Docker Compose, same Postgres pattern, same backup discipline โ privacy-clean, cookie-banner-free, GDPR-easy. The analytics endpoint is internal to the stack; nothing leaves the box. - Source: dev.to / 3 months ago
So this post is about something I've been chewing on for months but finally moved on: ripping Google Analytics out of three side projects and picking a privacy-focused alternative. Specifically, I'll compare Umami, Plausible, and Fathom โ the three I actually evaluated โ and walk through the migration steps that worked for me. - Source: dev.to / 3 months ago
Automated analysis tools: SonarQube, CodeClimate, and Codacy detect code-level debt automatically: cyclomatic complexity, code duplication, dependency staleness, and coverage gaps. These tools supplement but don't replace the architectural and business-logic debt that requires human judgment to identify and document. - Source: dev.to / 3 months ago
CodeClimate and Codacy can generate before/after metrics for code quality that make the starting and ending states concrete rather than subjective. - Source: dev.to / 3 months ago
CodeClimate quantifies maintainability so teams canโt hand-wave garbage away. - Source: dev.to / 10 months ago
Code Climate: Link - Automated code review and quality analysis for codebase health. - Source: dev.to / about 1 year ago
Use tools like SonarQube or CodeClimate to spot the high-risk 20%. Then fix one thing at a time not everything at once. This isnโt Dark Souls. - Source: dev.to / about 1 year ago
Plausible.io - Plausible Analytics is a simple, open-source, lightweight (< 1 KB) and privacy-friendly web analytics alternative to Google Analytics. Made and hosted in the EU, powered by European-owned cloud infrastructure ๐ช๐บ
Codacy - Automatically reviews code style, security, duplication, complexity, and coverage on every change while tracking code quality throughout your sprints.
Fathom Analytics - Simple, trustworthy website analytics (finally)
SonarQube - SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code.
Matomo - Matomo is an open-source web analytics platform
ESLint - The fully pluggable JavaScript code quality tool