Skip to content
CAI
Software that uses CAICheck a score

jhawthorn/vernier

59.7

Adequate · 6 November 2026

3.5k

lines of production code

Ruby

with C++

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Add heap and memory tracking capabilities

The extension now includes a HeapTracker and MemoryTracker, enabling users to profile object allocation, deallocation, and resident set size (RSS). HeapTracker records object lifecycles and stack traces via Ruby tracepoints, while MemoryTracker samples RSS at regular intervals on Linux and macOS. These features are exposed through new C++ source files (heap\_tracker.cc, memory.cc) and supporting infrastructure (stack\_table, periodic\_thread, signal\_safe\_semaphore).

ext · high confidence

Add instrumentation hooks for ActiveSupport notifications and memory usage

This change introduces two new profiling hooks within the \lib/vernier/hooks\ directory. The new \ActiveSupport\ hook subscribes to Rails notification events (excluding internal topics starting with \!\) and maps them to specific Firefox marker schemas for SQL queries, controller actions, cache operations, and view rendering, allowing users to visualize these framework activities in their performance profiles. Additionally, the new \MemoryUsage\ hook integrates with a memory tracker to record memory consumption samples over time, exposing this data as a dedicated counter in the profiler output.

lib/vernier/hooks · high confidence

Add vernier CLI entry point

A new executable script \bin/vernier\ has been added to the project. This script serves as the command-line interface entry point, delegating execution to the main implementation located in \exe/vernier\.

bin · high confidence

Initial release of Vernier, a next-generation Ruby sampling profiler

This change introduces Vernier, a new Ruby gem for profiling that supports Ruby 3.2.1+ on Unix-like systems. It provides command-line tools, Ruby APIs, and Rack middleware to capture time-based and retained-memory profiles, which can be visualized via Flame Graphs or Stack Charts in the Firefox profiler ecosystem. The release includes built-in hooks for ActiveSupport and memory usage, support for custom hooks with Firefox profiler integration, and configuration options for sampling intervals and allocation tracking.

(repo-wide) · high confidence

Introduce vernier CLI for profiling and viewing

Adds a new \vernier\ executable that provides \run\ and \view\ subcommands. The \run\ command profiles a target command with configurable sampling intervals, allocation tracking, signal-based start/stop, and instrumentation hooks (e.g., Rails), outputting profiles in Firefox or cpuprofile formats. The \view\ command displays profiling results as an inverted call tree and file listing, supporting gzip-compressed input files.

exe · high confidence

New output formats: Chrome CPU profile, Markdown, and CLI 'top' table

Vernier now supports generating profiles in the Chrome DevTools CPU profile format (cpuprofile.rb), a Markdown report for AI-friendly consumption (markdown.rb), and a terminal 'top'-style table (top.rb). The Markdown output includes a summary of metrics (mode, duration, samples, threads), user metadata, and tables of top hotspots by self and total time. The Chrome CPU profile output converts the internal multi-threaded profile into the single-threaded format expected by Chrome DevTools, mapping stack tables to nodes and calculating time deltas. The 'top' output provides a quick, limited-row view of the most sampled functions in the CLI. These additions complement the existing Firefox profiler and HTML file listing outputs.

lib/vernier/output · high confidence

New profiling examples for advanced concurrency and framework integration

Added a suite of new example scripts demonstrating Vernier's capabilities with complex Ruby concurrency patterns and frameworks. These include \custom\_hook.rb\ for integrating custom event markers, \fiber\_stalls.rb\ and \gvl\_sleep.rb\ for analyzing GVL and fiber scheduling behavior, \rails.rb\ for tracing Rails applications with configurable versions and allocation sampling, \ractor.rb\ for Ractor-based concurrency, \minitest.rb\ for parallel test profiling, and \threaded\_http\_requests.rb\ for multi-threaded network I/O. Additionally, \measure\_overhead.rb\ provides a benchmarking tool to compare profiler overhead against baseline performance.

examples · high confidence

Vernier profiler v1.11.0: New memory retention analysis and output formats

Vernier now includes a RetainedCollector and MemoryLeakDetector to profile retained memory usage, allowing users to identify objects preventing garbage collection. The profiler supports writing results in Firefox, cpuprofile, and Markdown formats, with gzip compression enabled by default for JSON output. A new Rack middleware allows on-demand profiling via URL parameters, and the autorun mode now supports toggling the profiler via a configurable signal.

lib/vernier · high confidence

Removals

Removal of Vernier RBS signature file

The RBS signature file for the Vernier module (sig/vernier.rbs) has been deleted, removing the type definition for the VERSION constant and associated documentation comments.

sig · high confidence

Behavioural changes

New profiling API with start/stop and multiple output formats

Vernier now exposes a structured profiling API via \Vernier.profile\ (aliased as \trace\ and \run\) and a stateful \Vernier.start\_profile\/\stop\_profile\ pair for long-running applications. The library has been refactored to support multiple output formats including Firefox profiler, cpuprofile, Markdown, and top, alongside new capabilities like heap tracking via \HeapTracker\ and memory leak detection. Users can now configure collector options such as allocation sample rates and benefit from improved thread handling and marker recording.

lib · high confidence

Test coverage

Added test coverage for Vernier output formats; Expanded test coverage for profiling features and output formats.

Dependencies

Update gem metadata and add development dependencies

The gemspec now includes a proper summary, description, and homepage URL, replacing the previous TODO placeholders. The required Ruby version has been raised to 3.2.1 (with an environment variable override available) to align with the project's focus on next-generation profiling. Additionally, development dependencies for activesupport, gvltest, and rack have been added, while the Gemfile now explicitly includes the cgi, benchmark-ips, and zlib (\>= 3.2.1) gems to support testing and CI stability.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.

Score

  • CAI 60 → 60 (-0.2)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 58 → 60 (+1.9)
  • Architecture 100 → 100 (+0.0)
  • Maturity 54 → 54 (+0.0)
  • Readiness 55 → 58 (+3.2)
  • Security 93 → 70 (-22.8)
  • Domain Modelling 100 → 100 (+0.0)
  • Performance 80 → 80 (+0.0)

Resolved (10)

  • Ambiguous duplication of profiling initiation. profile implies a synchronous or blocking operation that returns a result, while start_profile implies an asynchronous or stateful operation requiring a subsequent stop_profile. It is unclear if profile is a convenience wrapper for start_profile + stop_profile, or if they serve distinct concurrency models. This creates confusion for users regarding control flow.
  • High: security finding (details withheld)
  • High: security finding (details withheld)
  • High: security finding (details withheld)
  • High: security finding (details withheld)
  • Inconsistent method arity for the same operation. track exists in two forms: one taking a block (likely for scoped tracking) and one taking no arguments (likely for global/stateful tracking). While technically distinct signatures, the shared name without clear contextual differentiation in the signature (e.g., track_block vs track_global) can lead to usage errors.
  • Medium: security finding (details withheld)
  • Off-boarding risk: anonymized user #1
  • Redundant constructor signatures. In Ruby, new typically calls initialize. Exposing both as distinct public API methods on the type surface suggests either a misunderstanding of Ruby conventions or an unnecessary duplication of the entry point for instantiation.
  • Secret passed as a command-line argument

New (11)

  • High: security finding (details withheld)
  • High: security finding (details withheld)
  • High: security finding (details withheld)
  • High: security finding (details withheld)
  • High: security finding (details withheld)
  • High: security finding (details withheld)
  • No SBOM
  • No artifact signing
  • No build provenance
  • Off-boarding risk: anonymized user #1
  • Unpinned build actions

Changes since last survey

  • 22 commits — 21 feature/other, 1 fixes

By area

  • .github/workflows — 7 commits
  • lib/vernier — 6 commits
  • (repo) — 5 commits
  • ext/vernier — 3 commits
  • test/test_memory_tracker.rb — 1 commit

Notable commits

  • fix: Merge pull request #191 from jhawthorn/fix-ready-thread-sampling
  • change: Add VERNIER_ASSERT: RUBY_ASSERT by default, RUBY_ASSERT_ALWAYS in CI
  • change: Add embed_sources option to include source code in profiles
  • change: Create a draft GitHub release from the version bump
  • change: Emit String pids in Firefox output
  • change: Emit null unregisterTime/processShutdownTime for unfinished threads
  • change: Harden the version bump workflow
  • change: Install bump once instead of using gem exec
  • change: Install gems into the system gem directory in the gem push workflow
  • change: Mark SQL and cache keys as sanitized strings in Firefox marker schema
  • change: Merge pull request #190 from jhawthorn/skip-mn-main-thread
  • change: Merge pull request #192 from jhawthorn/cleanup-ruby-32-compat
  • change: Merge pull request #194 from jhawthorn/profiler-cli-tests
  • change: Merge pull request #195 from jhawthorn/embed-sources
  • change: Only capture READY stacks for running threads
  • change: Output Firefox processed profile format version 76
  • change: Remove Ruby 3.2 GVL event handling
  • change: Skip the RSS test when the main thread uses M:N scheduling
  • change: Test the Firefox output in the Firefox profiler on CI
  • change: Trigger gem push from GitHub releases
  • …and 2 more

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

jhawthorn/vernier was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 6 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 6053771835b5438a26e96f14d99ac0e6b2c077e1 — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.2+preprod-5c4e66d9318b.