Repo brief: roidrage/lograge

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T15:08:19.840Z · commit e5caed777529

Verdict

Healthy — Strong maintenance signals

• Last commit 2mo ago
• 33+ active contributors
• Distributed ownership (top contributor 20% of recent commits)
• MIT licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

Lograge is a Rails gem that replaces Rails' verbose default request logging with a single, parseable line per request containing key-value pairs (method, path, controller, status, duration, etc.). It solves the production logging problem where Rails' multi-line output becomes unreadable when multiple processes dump logs to the same file, making monitoring and debugging nearly impossible. Modular architecture: lib/lograge.rb is the entry point; lib/lograge/log_subscribers/ contains listeners for ActionController and ActionCable events; lib/lograge/formatters/ holds 10+ output formatters (JSON, Logstash, L2MET, LTSV, Graylog2, CEE, etc.); lib/lograge/rails_ext/ patches Rails internals;…

Start here

Open these first:

• lib/lograge.rb — Main entry point and configuration interface that initializes Lograge's core functionality and exposes the public API.
• lib/lograge/railtie.rb — Rails engine integration point that hooks Lograge into the Rails initialization lifecycle and registers log subscribers.
• lib/lograge/log_subscribers/action_controller.rb — Core request logging interceptor that captures and formats HTTP controller action execution events.
• lib/lograge/formatters/json.rb — Primary JSON formatter implementation demonstrating the standard output format pattern for production logging.
• lib/lograge/log_subscribers/base.rb — Abstract base class defining the common logging interface that all event subscribers inherit from.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repo, install dependencies, and run the test suite:

git clone https://github.com/roidrage/lograge.git
cd lograge
bundle install
bundle exec rspec

To test against a specific Rails version, use one of the gemfiles:

BUNDLE_GEMFILE=gemfiles/rails_7.1.gemfile bundle install
BUNDLE_GEMFILE=gemfiles/rails_7.1.gemfile bundle exec rspec

Daily commands:

This is a library gem, not a runnable app. To test it:

bundle exec rspec

To use it in a Rails app, add to Gemfile and create an initializer (see README truncation: 'Enable it in an initializer or th...'). No server command; Lograge hooks into Rails' existing logger during app boot via the Ra…

…shortened for this brief.

Key cautions & unknowns

• Scorecard: default branch unprotected (0/10)
• Configuration quirk: Lograge must be enabled explicitly in an initializer; if not configured, Rails will still emit default verbose logs. Formatter availability: Not all formatters may be suitable for all…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.