HN Showcase
Back to browse
GitHub Repository

Tamper-evident audit logging with cryptographic verification.

1 starsTypeScript

I built a tamper-evident audit logging service to prevent DB rewrites

by ashish-barmaiya·Feb 25, 2026·2 points·1 comment
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainNiche Gem

Cryptographic proof audit logs can't be rewritten, even by DB admins.

Strengths
  • •Closes a hard problem: traditional audit logs can't prove history wasn't rewritten by insiders.
  • •Clean trust model: verification trusts only hash chains and external anchors (Git), not the service itself.
  • •Deliberately API-first and verification-centric; separation of concerns allows offline verification.
Weaknesses
  • •Nascent: zero GitHub stars, no production deployments mentioned, no performance data.
  • •External anchoring dependency (Git) adds operational overhead; unclear how frequent anchoring must be for guarantees.
Category
Security
Target Audience

Compliance engineers, security teams, high-assurance application builders

Similar To

Merkle-based audit systems · Verifact

Similar Projects

Security●●●Banger

Tamper evident audit logs for LangGraph/CrewAI agents

Cryptographic hash chains make agent action logs legally defensible—LangSmith and Langfuse don't do this.

Big BrainWizardrySolve My Problem
oabolade
101d ago
AI/ML●●Solid

Tamper-evident audit logs for LangChain/Crew AI agents

Cryptographic hash chains make AI agent logs legally defensible when LangSmith can't.

Niche GemBig Brain
oabolade
2012h ago