collectiveidea/audited

Audited (formerly acts_as_audited) is an ORM extension that logs all changes to your Rails models.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 19th, 2026
Created on February 9th, 2008
Open Issues & Pull Requests: 208 (+0)
GitHub issues: Enabled
Number of forks: 659
Total Stargazers: 3,498 (+0)
Total Subscribers: 34 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,346 days
Stale 30+ days: 19
Stale 90+ days: 18

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • feedback (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Audited is an ORM extension that logs all changes to your Rails models.

The tool addresses the need to maintain a complete audit trail of model modifications in Rails applications. It works by automatically creating audit records whenever a model is created, updated, touched, or destroyed, capturing what changed and optionally who made the change. Audits can include comments and associations to related models. By default, changes are stored in YAML format, though PostgreSQL users can opt for native JSON column types for better performance, and the user ID column type can be customized to support non-integer primary keys like UUIDs.

Audited suits Rails applications that require compliance tracking, change history, or accountability for data modifications. It works with ActiveRecord and supports a wide range of Rails versions. The tool allows fine-grained control through configuration: you can specify which columns to audit, which actions trigger audits, and whether to exclude certain callbacks globally. This flexibility means you can audit only the data that matters for your use case rather than tracking everything by default.

The project maintains active test coverage across multiple Ruby versions and Rails releases, with continuous integration validating compatibility. Development follows a structured code style standard and responds to upgrade requirements by providing migration generators that only apply necessary schema changes.