Project Summary
Tomb is a system to make strong encryption easy for everyday use. A tomb is like a locked folder that can be safely transported and hidden in a filesystem. Its keys can be kept separate; for example, you can keep the tomb on your computer and its key on a USB stick or a remote SSH shell.
Tomb is written in code that is easy to review and links shared components: it consists of a ZShell script and desktop integration apps; it uses standard GNU tools and the cryptographic API of the Linux kernel (dm-crypt) via cryptsetup.
Badges
In a Nutshell, Tomb, the Crypto Undertaker...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a average size development team
with decreasing Y-O-Y commits -
...
took an estimated 2 years of effort (COCOMO model)
starting with its first commit in August, 2010
ending with its most recent commit about 2 months ago
Quick Reference
GNU General Public License v3.0 or later
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Use Patent Claims
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
Include Install Instructions
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
you can embed statistics from Open Hub on your site
-
...
use of OSS increased in 65% of companies in 2016
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
30 Day SummaryJan 1 2026 — Jan 31 2026
|
12 Month SummaryJan 31 2025 — Jan 31 2026
|
