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

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
Target Audience

Compliance engineers, security teams, high-assurance application builders

Similar To

Merkle-based audit systems · Verifact

Similar Projects

Security●●●Banger

VellaVeto — blocks unsafe MCP tool calls by default

Fail-closed MCP gateway with formal verification and MCPSEC benchmark suite.

Big BrainWizardryZero to One
paolovella
212mo ago
Security●●Solid

Air – Open-source black box for AI agents (tamper-evident audit trails)

Instead of another observability dashboard, this project builds a provable audit trail: an OpenAI-compatible reverse proxy that vaults prompts in MinIO and links calls with an HMAC-SHA256 tamper-evident chain, plus replay tooling (replayctl) and Jaeger traces. The cryptographic audit chain and the one-line SDK wrap are clever and practical; the real operational work left to teams will be key management and storage/retention strategy.

WizardryNiche Gem
shotwellj
213mo ago