True/False fields have a great simplicity about them, and many times they're perfect for the job! But, it's not uncommon end up in a place where you'd really love to keep some degree of simplicity with a little more detail about when the value was changed. Sometimes you'll want to display that information to the user and other times you'll keep it for auditing or debugging purposes. Either way, boolean_timestamp makes the job easy from the beginning and adds very little code to your app.

Trail audit logs (Operation logs) into the database for user behaviors, including a web UI to query logs.

Pronto runner for bundler-audit, patch-level verification for bundler.

In frustration of Mongoid::Versioning, I created this plugin for tracking historical changes for any document, including embedded ones. It achieves this by storing all history tracks in a single collection that you define. (See Usage for more details) Embedded documents are referenced by storing an association path, which is an array of document_name and document_id fields starting from the top most parent document and down to the embedded document that should track history. This plugin implements multi-user undo, which allows users to undo any history change in any order. Undoing a document also creates a new history track. This is great for auditing and preventing vandalism, but it is probably not suitable for use cases such as a wiki.

This library tracks historical changes for any document, including embedded ones. It achieves this by storing all history tracks in a single collection that you define. Embedded documents are referenced by storing an association path, which is an array of document_name and document_id fields starting from the top most parent document and down to the embedded document that should track history. Mongoid-history implements multi-user undo, which allows users to undo any history change in any order. Undoing a document also creates a new history track. This is great for auditing and preventing vandalism, but it is probably not suitable for use cases such as a wiki.

ICFS is a case management and filing system, developed for investigative cases, but generally applicable to many types of work. It provides a structured way to store and retrieve information, a case-focused access control scheme which can integrate into existing identity and access management systems, a flexible way to manage and track work assignments, and a way to gather statistics which is flexible and can be audited.

A powerful auditing logging system

This tool is just a simple checker to see if newer versions of Carthage dependencies use keywords that relate to security

Perfect Audit API wrapper. https://www.ocrolus.com/api-doc/

Tool for auditing events.

Audit

Show changed attributes of ActiveRecord model

run code quality and security audit report with one command or one rake task

A Sequel plugin that logs changes made to an audited model, including who created, updated and destroyed the record, and what was changed and when the change was made. This plugin provides model auditing (a.k.a: record versioning) for DB scenarios when DB triggers are not possible. (ie: on a web app on Heroku).

Fluentd Filter Plugin to parse linux's audit log.

Every update on audited table will be logged. You can update in bulk

Execute audited asynchronously with ActiveJob.

It is a library for parsing.

bundler-budit is a fork of bundler-audit, which provides patch-level verification for Bundled apps.

Redmine plugin for checking Redmine's own vulnerabilities