CodeVitals
Analyzes GitHub repositories to score engineering team health on output, quality, and process metrics.
≈ 5visits/mo
Emerging · estimate, read 2026-09-19
- For
- Engineering managers and founders who need to understand their dev team's productivity without reading code.
- Price
- Free plan · From $149/mopricing page, read 2026-09-20
- Activity
- Maintainednothing dated on the site
- Company
- founding year not on record
- Track whether code is being shipped and reviewed consistently
- Identify bottlenecks slowing down team workflow and delivery
- Detect AI-generated commits to assess code quality patterns
- #5
PostHog
Ingests product data and runs AI agents to investigate issues and recommend product improvements.
24.7knot readFree plan2020 - #23
GrowthBook
Runs A/B tests, manages feature flags, and analyzes product data from your data warehouse.
34.8kActiveFrom $40/user/mo2020 - #28
Weights & Biases
Tracks machine learning experiments, manages models and datasets, and monitors AI applications in production.
21.2kMaintainedFrom $60/mo - #29
ReadMe
Publishes and maintains API documentation with AI-assisted writing, version control, and developer analytics.
40.4kActiveFrom $250/mo - #37
Inspectlet
Records visitor sessions and heatmaps to show how users interact with websites.
3.5kMaintainedFrom $39/mo - #44
Tinybird
Managed ClickHouse platform for building real-time analytics APIs and data products with serverless infrastructure.
12.1kActive—
What is CodeVitals?
Analyzes GitHub repositories to score engineering team health on output, quality, and process metrics.
Who is CodeVitals for?
Engineering managers and founders who need to understand their dev team's productivity without reading code.
How much does CodeVitals cost?
CodeVitals has a free plan; paid plans start at $149/mo, per its pricing page on 2026-09-20.
Do people use CodeVitals?
Emerging: ≈ 5 visits a month · estimate, 2026-09.
Is CodeVitals still maintained?
Maintained.
What are alternatives to CodeVitals?
In Developer tools, by use: PostHog, GrowthBook, Weights & Biases, ReadMe, Inspectlet, Tinybird.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.