Repo brief: DatabaseCleaner/database_cleaner

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T22:43:58.879Z · commit f50ccb2f9c60

Verdict

Mixed — Slowing — last commit 10mo ago

• Last commit 10mo ago
• 20 active contributors
• Distributed ownership (top contributor 45% 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

What it is

database_cleaner is a Ruby gem framework that provides pluggable strategies for clearing test databases across multiple ORMs (ActiveRecord, Sequel, Mongoid, Redis, etc.) and databases (MySQL, PostgreSQL, SQLite, MongoDB). It ensures a clean database state between tests by supporting deletion, truncation, and transaction-based approaches, eliminating test data pollution without writing ORM-specific cleanup code. Monorepo structure with lib/database_cleaner/ containing the core strategy system (lib/database_cleaner/cleaner.rb manages individual cleaners, lib/database_cleaner/cleaners.rb orchestrates multiple). Separate database_cleaner-core.gemspec and database_cleaner.gemspec split core…

Start here

Open these first:

• lib/database_cleaner.rb — Main entry point that exports the public API and initializes all core cleaning infrastructure.
• lib/database_cleaner/cleaner.rb — Core Cleaner class that manages database-specific cleaning strategies and orchestrates the cleaning lifecycle.
• lib/database_cleaner/strategy.rb — Base Strategy class that all database-specific cleaning implementations inherit from; defines the interface contract.
• lib/database_cleaner/cleaners.rb — Manages multiple cleaner instances across different databases and ORM configurations.
• lib/database_cleaner/core.rb — Core module providing low-level initialization, configuration, and state management for all cleaners.

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.

git clone https://github.com/DatabaseCleaner/database_cleaner.git && cd database_cleaner && bundle install && bundle exec rake && bundle exec cucumber

Daily commands:

bundle exec rspec (for unit tests, implied by .rspec config) or bundle exec cucumber (for integration tests in features/ and examples/features/). Use Guardfile (bundle exec guard) for continuous test running during deve…

…shortened for this brief.

Key cautions & unknowns

• Slowing — last commit 10mo ago
• database_cleaner delegates to ORM-specific adapter gems (database_cleaner-active_record, etc.), so core lib/ won't work without loading an adapter—this is by design but catches new users. The Safeguard checks for…
• 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

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.