Taking over the Audit Trail namespace

I would like to take over the Audit Trail namespace on drupal.org to publish a modern Drupal 11 audit-trail module that I have been developing.

State of the existing project

The existing drupal/audit_trail project has not seen actual code commits since 2012; the only commit after that (in 2014) removed a stale SimpleTest file. It was never ported beyond Drupal 7, has no tagged releases, and is not covered by Drupal's security advisory policy.

• Default branch: master, last commit 2012-09-13 ("Adding README.txt")
• Branches present: 6.x-1.x (last commit 2014-06-23), 7.x-1.x (2012-09-13), master (2012-09-13)
• No 8.x / 9.x / 10.x / 11.x branches
• No tagged releases

The existing codebase implements a form-submission logger: it matches form IDs or paths against regex patterns and writes submissions to a custom file or watchdog, with password fields replaced by the literal string Hidden. The scope of the replacement module below is different (entity-CUD audit trail, HMAC-chained tamper-evidence) so there is no semantic overlap to preserve, but the existing branches and history will not be deleted.

What I would publish

A complete rewrite targeting Drupal 11, currently hosted at gitlab.com/acte-generator-project/audit_trail, providing:

• A canonical write API (created / updated / deleted / event) with audit-shaped indexed storage (action, resource, before, after columns).
• HMAC-chained tamper-evidence with a runtime integrity verifier and a cron-driven chain verification job that surfaces under hook_runtime_requirements.
• An admin viewer with side-by-side before/after diff.
• A chained PSR-3 logger exposed as a generic service, so any module can route entries into the audit chain via chain: TRUE in the log context.
• A generic per-type entity CUD bridge as a submodule (audit_trail_entity).
• Designed for auditable systems (notarial, eIDAS, compliance, change tracking).

Transition pledge

If the namespace is granted:

• Existing branches (master, 6.x-1.x, 7.x-1.x) and their git history will be preserved.
• A new branch will host the modern code, with the legacy branches left in place for reference.
• I will document the transition (scope change, migration notes if relevant) in the project README and in the issue queue.

Current maintainers contacted

• -enzo-
• kevin-hankens
• nagba

Supporting organisation: weKnow Inc.

I will contact all three via drupal.org contact forms with a pointer to this issue.