codenotary/immudb

immudb - immutable database based on zero trust, SQL/Key-Value/Document model, tamperproof, data change history

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 7th, 2026
Created on November 7th, 2019
Open Issues & Pull Requests: 110 (+0)
GitHub issues: Enabled
Number of forks: 378
Total Stargazers: 9,029 (+0)
Total Subscribers: 79 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.0 days
Mean response time: 203.6 days
90th percentile: 846.6 days
Tracked items: 63

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 6% of issues opened in the past year have been closed. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

immudb is an immutable database that provides cryptographic proof and verification of data integrity without requiring trust in the database itself.

The tool addresses the problem that traditional databases maintain mutable transaction logs, making it impossible to detect tampering with historical data. immudb solves this by making all data immutable—new versions of records can be added but existing records cannot be changed or deleted. It uses cryptographic coherence to protect the integrity of the history, with verification performed by clients rather than relying on server-side guarantees. The database operates across three data models: key-value, document, and relational SQL, and can handle millions of transactions per second while remaining lightweight enough to run on IoT devices, embedded in applications as a Go library, or deployed in cloud environments.

Organizations should adopt immudb when they need tamper-evident storage for sensitive or auditable data, such as transaction logs, sensor readings, compliance records, or software artifacts. It suits projects requiring cryptographic verification of data history without the performance overhead of blockchain systems. The tool is particularly valuable for regulated industries where data integrity and audit trails are mandatory. Unlike traditional databases, immudb guarantees that historical data cannot be silently modified, making it suitable for security-critical applications where the immutability guarantee itself is a core requirement rather than an optional feature.

The project maintains active development with regular updates and improvements to its SQL compatibility layer and security hardening features. The codebase demonstrates ongoing refinement of core functionality including structured audit logging capabilities and query diffing for relational data. The tool has achieved substantial adoption in production environments across diverse use cases, from compliance logging to artifact verification.