Argus-seal – Forensic-ready log integrity using Merkle Trees
Argus-seal – Forensic-ready log integrity using Merkle Trees
I built Argus-seal because standard log hashing (like SHA256 on a flat file) makes it impossible to pinpoint which specific entry was tampered with in a massive dataset. It uses a Merkle Tree structure to "seal" log batches. The core value-add is the "Strict Mode" verification: it doesn't just return a boolean, but traverses the tree to identify the exact index of the compromised log entry in O(N *log N) time. Key Technical Highlights: - Deterministic Canonicalization: Ensures that JSON/Dict entries produce identical hashes regardless of key ordering. - Granular Diagnostics: Pinpoint specific tampered leaves without re-hashing the entire historical log. - Lightweight & FOSS: Zero-dependency Python implementation designed for easy integration.I’m looking for feedback on the tree traversal logic and whether this approach satisfies real-world compliance (SOC2/HIPAA) requirements. I'd love to hear your thoughts or "roasts" on the implementation! GitHub: https://github.com/gamer-null/argus-seal
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
Log Aggregation using Logrange. Use it in k8s or standalone
Burger log
ActiveMQ/Openwire appender for Logback. Log with reliability guarantees
Targeted Log Levels
Takipi 2.0 – Stop Using Log Files
AIOps MCP – Log anomaly detection using Isolation Forest
Procedural log cabins using code CAD
I built a web-ready synthesizer using WebAssembly and C++
Cross-applicative Log correlation using AI
Log the Crux – A rock climbing log book