active_analytics

First-party, privacy-focused traffic analytics for Ruby on Rails applications.

Runs with mockssource: GitHubRubyMITcommit c63036148abf

Ruby, MIT licensed. The project labels itself: analytics, privacy, rails, ruby and trafic analytics.

active_analytics runs, with stand-ins for the services it depends on. An Argusic agent installed it in 19 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

ActiveAnalytics gem builds, database migrations run, and all 7 existing tests pass (4 sync record_request tests verify real SQLite persistence, 1 async queue test passes with MockRedis, 2 model tests verify database validations).

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.14 (measured)
recorded runs
1
last tested
stars
515
forks
13
open issues
1
watchers
11
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing active_analytics, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Bundler version conflicts between site_ruby and default lib/ruby in Traveling Ruby5 minutes
  • Gemfile.lock versions unavailable in pre-installed Traveling Ruby gems3 minutes
  • No Redis server available for async queue tests3 minutes
  • No Ruby installed in container2 minutes
  • redis gem not pre-installed (only redis-client)1 minute
Install time
19 minutes
Cold machine to finish
19 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
Model tokens used
292,500
Exact commit tested
c63036148abf
Container image
sha256:4c3d41857be3

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

How the result was proved
runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Here's my report. The key challenge was that the container had no Ruby installed, so I had to bring…
**Errors encountered:**
1. **No Ruby installed** — Installed Traveling Ruby 3.2.9 (precompiled static) from `trubygems/trav…
2. **Bundler version conflicts** (Traveling Ruby had both bundler 2.2.22 in gems and 2.7.2 in site_…
3. **Gemfile.lock pinned to unavailable gem versions** (sqlite3 2.6.0, redis 5.4.0 not pre-installe…
4. **No Redis server** — Created `MockRedis` class for test environment
5. **Missing `redis` gem** (only `redis-client` was pre-installed) — Installed it via `gem install …
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
 succeeded in 0ms:
tokens used
292,500

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 19 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 13 analytics projects Argusic has installed and timed, active_analytics was the 8th fastest to reach a running state, and 10 of 13 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.14

Topics (from GitHub)

analyticsprivacyrailsrubytrafic-analytics

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/active_analytics.svg)](https://argusic.com/subject/active-analytics)

Questions

Does active_analytics run?
active_analytics runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 19 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test active_analytics?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c63036148abf. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test active_analytics?
The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does active_analytics take to install?
19 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does active_analytics need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing active_analytics?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does active_analytics compare with the alternatives?
Of the 13 analytics projects Argusic has installed and timed, active_analytics was the 8th fastest to reach a running state, and 10 of 13 reached one at all.
Where is the evidence for active_analytics?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion