Implement tamper-evident audit logs#151
Merged
Obiajulu-gif merged 2 commits intoJul 27, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implemented tamper-evident audit logging for sensitive administrative and financial actions. This adds append-only hash-linked audit events, canonical serialization, checkpoint signing, legacy audit migration, filtered exports with integrity manifests, and offline export verification.
Related Issue
Closes #106
Affected Areas
Checklist
Screenshots
Not applicable.
Additional Notes
Validation run:
npm run typecheckpassednpx vitest run lib/security/audit-hash.test.tspassednpm run lintpassed with 2 existing warnings outside this change