HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
FiloSottile
age
Go2019–2026
FiloSottile / age

age

A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.

107Distinct people
126Mentions
1Explicit recommenders
24.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I recommend age as well. It offers encrypting for recipients for whom you have public keys. https://github.com/FiloSottile/age

ChrisGranger used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year126 dated mentions

Observed mentions: 2019-10-07 03:21:46 UTC to 2026-10-10 15:30:33 UTC.

01020302019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 11 mentions; 4 submissions, 7 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 15 mentions; 0 submissions, 15 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 29 mentions; 7 submissions, 22 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 24 mentions; 5 submissions, 19 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 16 mentions; 3 submissions, 13 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC1147
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC15015
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC29722
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC24519
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC12012
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC12210
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC16313
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC725

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
age is a simple, modern and secure file encryption tool, format, and Go library. It features small explicit keys, post-quantum support, no config options, and UNIX-style composability. $ age-keygen -o key.txt Public key: age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p $ tar cvz ~/data | age -r age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p > data.tar.gz.age $ age --decrypt -i key.txt data.tar.gz.age > data.tar.gz 📜 The format specification is at age-encryption.org/v1. age was designed by @benjojo and @FiloSottile. 🦀 An alternative interoperable Rust implementation is available at github.com/str4d/rage. 🌍 Typage is a TypeScript implementation. It works in the browser, Node.js, Deno, and Bun. 🔑 Hardware PIV tokens such as YubiKeys are supported through the age-plugin-yubikey plugin. ✨ For more plugins, implementations, tools, and integrations, check out the awesome age list. 💬 The author pronounces it [aɡe̞] with a hard g, like GIF, and it's always spelled lowercase. Installation Homebrew (macOS or Linux) brew install age MacPorts port install age Windows winget install --id FiloSottile.age Alpine Linux v3.15+ apk add age Arch Linux pacman -S age Debian 12+ (Bookworm) apt install age Debian 11 (Bullseye) apt install age/bullseye-backports (enable backports for age v1.0.0+) Fedora 33+ dnf install age Gentoo Linux emerge app-crypt/age Guix System guix package -i age NixOS / Nix nix-env -i age openSUSE Tumbleweed zypper install age Ubuntu 22.04+ apt install age Void Linux xbps-install age FreeBSD pkg install age (security/age) OpenBSD 6.7+ pkg_add age (security/age) Chocolatey (Windows) choco install age.portable Scoop (Windows) scoop bucket add extras && scoop install age On Windows, Linux, macOS, and FreeBSD you can use the pre-built binaries. https://dl.filippo.io/age/latest?for=linux/amd64 https://dl.filippo.io/age/v1.3.2?for=darwin/arm64 ... If you download the pre-built binaries, you can check their Sigsum proofs. If your system has a supported version of Go, you can build from source. go install filippo.io/age/cmd/...@latest Help from new packagers is very welcome. Usage For the full documentation, read the age(1) man page. Usage: age [--encrypt] (-r RECIPIENT | -R PATH)... [--armor] [-o OUTPUT] [INPUT] age [--encrypt] --passphrase [--armor] [-o OUTPUT] [INPUT] age --decrypt [-i PATH]... [-o OUTPUT] [INPUT] Options: -e, --encrypt Encrypt the input to the output. Default if omitted. -d, --decrypt Decrypt the input to the output. -o, --output OUTPUT Write the result to the file at path OUTPUT. -a, --armor Encrypt to a PEM encoded format. -p, --passphrase Encrypt with a passphrase. -r, --recipient RECIPIENT Encrypt to the specified RECIPIENT. Can be repeated. -R, --recipients-file PATH Encrypt to recipients listed at PATH. Can be repeated. -i, --identity PATH Use the identity file at PATH. Can be repeated. --version Print the version. INPUT defaults to standard input, and OUTPUT defaults to standard output. If OUTPUT exists, it will be overwritten. RECIPIENT can be an age public key generated by age-keygen ("age1...") or an SSH public key ("ssh-ed25519 AAAA...", "ssh-rsa AAAA..."). Recipient files contain one or more recipients, one per line. Empty lines and lines starting with "#" are ignored as comments. "-" may be used to read recipients from standard input. Identity files contain one or more secret keys ("AGE-SECRET-KEY-1..."), one per line, or an SSH key. Empty lines and lines starting with "#" are ignored as comments. Passphrase encrypted age files can be used as identity files. Multiple key files can be provided, and any unused ones will be ignored. "-" may be used to read identities from standard input. When --encrypt is specified explicitly, -i can also be used to encrypt to an identity file symmetrically, instead or in addition to normal recipients. Multiple recipients Files can be encrypted to multiple recipients by repeating -r/--recipient. Every recipient will be able to decrypt the file. $ age -o example.jpg.age -r age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p \ -r age1lggyhqrw2nlhcxprm67z43rta597azn8gknawjehu9d9dl0jq3yqqvfafg example.jpg Recipient files Multiple recipients can also be listed one per line in one or more files passed with the -R/--recipients-file flag. $ cat recipients.txt # Alice age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p # Bob age1lggyhqrw2nlhcxprm67z43rta597azn8gknawjehu9d9dl0jq3yqqvfafg $ age -R recipients.txt example.jpg > example.jpg.age If the argument to -R (or -i) is -, the file is read from standard input. Post-quantum keys To generate hybrid post-quantum keys, which are secure against future quantum computer attacks, use the -pq flag with age-keygen. This may become the default in the future. Post-quantum identities start with AGE-SECRET-KEY-PQ-1... and recipients with age1pq1.... The recipients are unfortunately ~2000 characters long. $ age-keygen -pq -o key.txt $ ag
Read the full README on GitHub

What Hacker News says

12 sources
> something fresh It exists, it's called age.. Some random links https://github.com/FiloSottile/age https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age... https://github.com/FiloSottile/age/discussions/432 > (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails.. Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93
In A Schism in the OpenPGP World
None of the existing password managers filled my need, so i started to write my own (not the crypto ofcourse). Here it is :) Why did I do it? I'm totaly dependend on my password managing software, all my passwords are generated by random so non of them are rememberable. During the last years I felt that my expectations and the traits of the password manager I was using grew appart. I dislike subscription based software (especialy if i might need it to extract/recover my secrets out of an old file). I dislike Web-UIs in native Apps. So i was looking around but when I had an incident where a licensed password vault just forgot that it was licenced and denied access I had enough. I wanted something that had a UI but also a data format that enables recovery with very little tools. So thats what I started to create. A-Pass saves its secret
Read the rest
s as json content encrypted by age[1] (so no hasseling with gpg). No information is visible without decrypting the files (no names / no urls). The file structure should be easy to sync, but its not implemented yet. Looking forward to input & comments :) [1] https://github.com/FiloSottile/age
In Show HN: A-Pass – small little password manager
As a text format anti-fan, I recently took a stab at defining a binary file format that's semantically equivalent to Age (more or less) [1]. It's currently just a draft/prototype/PoC, although I'd be interested to get some more eyes on it. Conceptually, it should be possible to implement compatibility with Age's plugin ecosystem, although I haven't done that yet (and I haven't thought about potential cryptographic implications of doing so, either). I've written a bit more about my rationale and why I'd prefer a simple binary format here [2] - notably, I found two text parsing bugs (of low/moderate severity) in existing Age implementations. [1] https://github.com/DavidBuchanan314/bagel [2] https://github.com/FiloSottile/age/discussions/497
In Age: Modern file encryption format with multiple pluggable recipients

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.