PAGES
← all tools
◆ Data Security & DLP

Clevis

v24 open-source

Pluggable framework for automated decryption of data and automated unlocking of LUKSLUKSA disk-encryption standard built into the Linux kernel that stores encryption metadata in a header on the volume itself, letting cyber tools unlock encrypted drives portably across distributions and implementations. volumes using pins like Tang, TPMTPMA dedicated hardware chip, standardized by the Trusted Computing Group, that stores cryptographic keys and measurements in tamper-resistant silicon, giving cyber tools a root of trust that software alone cannot fake., and PKCS#11PKCS#11The standard programming interface software uses to ask an HSM, smart card or token to sign or decrypt with a key it holds. Supporting it lets a tool keep its keys in hardware..

Summary

Clevis is an open-source, free command-line framework for automated decryption, used to unlock encrypted data or LUKS disk volumes without a human entering a passphrase at boot. It works through pluggable pins — Tang for network-bound key servers, TPM1 and TPM2 for hardware-backed keys, and an experimental PKCS#11 pin for hardware tokens — with each encrypt or decrypt operation run as a simple shell command. It suits systems administrators and platform engineers who need disks or secrets to unlock automatically on trusted hardware or networks, rather than application developers managing config values. It sits in the disk-encryption and automated-unlock space alongside LUKS tooling, integrating at the initramfs level so volumes come up unattended on boot. First committed in 2015 and still active, with 60 contributors and 19 commits in the past year.

Pluggable framework for automated decryption of data and automated unlocking of LUKS volumes using pins like Tang, TPM, and PKCS#11.

How Clevis helps

Which LUKS volumes on this machine will unlock themselves at boot, and which ones still wait on a passphrase?

lists the bindings recorded on each device's metadata, showing which pin secured each one

Can this disk unlock itself if it's moved to another machine or network?

depends on the pin bound to it — a network-bound Tang binding needs the original server reachable, while a TPM-backed one is tied to that specific hardware, so the binding metadata tells you which condition must hold

Will this volume still come up unattended after a policy or key change on the server side?

re-requests the key advertisement at decrypt time and checks it against what was trusted at encrypt time, so a changed or untrusted advertisement blocks the automatic unlock

Is this encrypted data recoverable without someone typing a passphrase in?

decrypts the stored JWE object directly using whatever pin secured it, with no interactive input required if the bound condition (network server, TPM, token) is satisfied

Which hardware-backed option should secure a volume on a machine with an older TPM chip versus a newer one?

offers separate TPM1 and TPM2 pins, with the TPM2 pin auto-selecting a PCR algorithm bank the installed chip actually supports

Will this volume still unlock automatically once its root filesystem switches over from the initramfs?

depends on whether the needed pin binary and any HTTPS trust material were copied into the initrd, so a missing pin or certificate bundle there breaks the automatic unlock after boot continues past early userspace

all 12 features, with the evidence for each →

Languages

Not documented

Features

12 capabilities · 1 backed by code, an API document or a real run

Built from Clevis's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Clevis covers 1 of the 8 data discovery and protection capabilities we track.

What Clevis offers you

  • Command-line interface3
Encryption at rest 7 features Data discovery and protection since 2020
TPM1 Pin Support shipped Enables Clevis-based automated decryption on legacy hardware with TPM 1.2 chips. 4 releases · first seen Feb 2021

Shared capability: Encryption at rest

release

  • Drops the network dependency from the TPM1 dracut module, so TPM1 unlocking no longer requires network availability at boot. v24 · Oct 2026 · source · release history
  • Adds a Meson build option to make the tpm1 pin optional, allowing packagers and builders to exclude TPM 1.2 support from the binary. v23 · May 2026 · source · release history
  • Adds TPM 1.2 support via a new tpm1 pin, enabling Clevis-based automated decryption on legacy hardware with TPM 1.2 chips. v23 · May 2026 · source · release history
  • Adds support for TPM2-tools 5.X in the tpm2 pin v16 · Feb 2021 · source · release history
Non-Interactive LUKS Binding shipped Supports non-interactive execution for binding LUKS devices by providing an assume-yes flag and suppressing user prompts. 2 releases · 1 other source · first seen Oct 2020

Shared capability: Encryption at rest

Also counts toward: Command-line interface

release

  • Passes --force-password to luksChangeKey to bypass pwquality/cracklib checks for Clevis-generated random keys. v24 · Oct 2026 · source · release history
  • Adds -y (assume yes) argument to clevis luks bind to enable non-interactive execution v15 · Oct 2020 · source · release history

example

  • Non-interactively bind a LUKS device to a Tang server without user prompts. clevis luks bind -d /dev/sda1 tang '{"url":"http://tang.example.com"}' -y v15 · Oct 2020 · source
LUKS Policy Re-binding shipped Enables re-binding a LUKS volume with an updated policy, such as changing the Tang server URL, using non-interactive or interactive modes. 2 releases · first seen Oct 2020

Shared capability: Encryption at rest

Also counts toward: Command-line interface

release

  • Adds proper support for binary keyfiles in Clevis operations v16 · Feb 2021 · source · release history
  • Introduces clevis luks regen command to re-bind a LUKS volume with updated policy v15 · Oct 2020 · source · release history
LUKS Binding Status Reporting shipped Allows users to inspect and display the current binding status, encryption policy, and token IDs of a bound LUKS device. 1 release · 1 other source · first seen Oct 2020

Shared capability: Encryption at rest

Also counts toward: Command-line interface

release

  • Introduces clevis luks report command to display current LUKS binding status v15 · Oct 2020 · source · release history

example

  • Inspect the current encryption policy and token IDs of a bound LUKS device. clevis luks report -d /dev/sda1 v15 · Oct 2020 · source
JWE Decryption shipped Decrypts JWE objects without user interaction. 1 release · 1 other source · first seen Aug 2020

Shared capability: Encryption at rest

release

  • Improved support for unlocking multiple LUKS devices on boot v14 · Aug 2020 · source · release history

example

  • Decrypt a JWE object without interaction clevis decrypt < CIPHERTEXT.jwe > PLAINTEXT
Initrd Integration shipped Automatically installs necessary TPM2 pins and CA certificate bundles into the initramfs for early boot unlocking. 1 release · first seen Mar 2026

Shared capability: Encryption at rest

release

  • Installs clevis-pin-tpm2 into the initrd automatically when the TPM2 pin is required. v22 · Mar 2026 · source · release history
Non-Block Device Unlocking shipped Supports unlocking non-block-device volumes such as loop files and network-backed volumes. 1 release · first seen Mar 2026

Shared capability: Encryption at rest

release

  • Supports unlocking non-block-device volumes (e.g. loop files, network-backed volumes) via clevis-luks-askpass. v22 · Mar 2026 · source · release history
Other / not yet classified 5 features Features we have not matched to a capability yet. A suggested match is marked.
Network Requirement Configuration shipped Controls whether the dracut unlocker automatically appends the network requirement flag, allowing for manual network setup when needed. 3 releases · first seen Aug 2020

release

  • Orders clevis-luks-askpass after network-online.target in the tang dracut module when systemd is included, ensuring network is ready before tang unlock is attempted. v24 · Oct 2026 · source · release history
  • The dracut unlocker no longer automatically appends rd.neednet=1, requiring manual network setup when using tang. v14 · Aug 2020 · source · release history
  • rd.neednet=1 is no longer added automatically by the dracut unlocker v14 · Aug 2020 · source · release history
Authenticated Tang Connections shipped Provides optional mutual TLS to authenticate Tang server connections during the unlock process. 1 release · first seen Oct 2026

release

  • Adds optional mutual TLS (mTLS) support to the tang pin for authenticated tang server connections.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v24 · Oct 2026 · source · release history
PKCS#11 Token Support shipped suggested Enables early boot unlocking using PKCS#11 compatible hardware tokens by including required libraries in the initrd. 1 release · first seen Oct 2026

Suggested capability: Encryption at rest. This is our guess, not confirmed.

release

  • Includes libpcsclite_real.so in the dracut initrd PKCS#11 module to enable PKCS#11 token access during early boot on distributions that ship the library. v24 · Oct 2026 · source · release history
PIN Template and Sample Files shipped Provides documentation and sample PIN templates to help authors write custom Clevis pins. 1 release · first seen Mar 2026

release

  • Adds a pin template with documentation and a sample file pin to help authors write custom Clevis pins. v22 · Mar 2026 · source · release history
Target naming verified Allows the user to assign a name to a scan target or session via the -n flag. 1 other source · first seen Oct 2017

command line

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Clevis, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Clevis puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

7 entries

  1. October 20261
  2. May 20261
  3. March 20261
  4. September 20241
  5. February 20211
  6. October 20201
  7. August 20201
    Show

    7 entries

    Project health

    Issue, contributor and maintainer activity in latchset/clevis, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 9 −3 vs prior 12 months
    2. Maintainers 3 +3 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 95% of issues opened, last 12 months
    5. Median time to close 425 days first maintainer reply 11 hours
    6. Open backlog 148 of 323 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 148
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,258
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →