hanko(1)

🌸 NAME 🌸

ok so bestie, welcome to the hanko(1) manual page 💖 — like, yes, that's the manual name and the page name, they match, iconic. Here's the whole vibe:

hanko — keeps your Git allowed signers file up to date with signing keys configured on software development platforms like GitHub and GitLab. literally that's the entire job. no cap.

---

✨ SYNOPSIS ✨

hanko [-v|--verbose]... [-c|--config] [--file] [-h|--help] <subcommands>

that's the whole shape of it 🫶 flags first, subcommand last, and the flags are optional (the square brackets said so, not me).

---

🦋 DESCRIPTION 🦋

okay so picture this: you've got signing keys chilling on software development platforms like GitHub and GitLab, and you've got a Git allowed signers file that's supposed to know about them.

hanko keeps your Git allowed signers file up to date with signing keys configured on software development platforms like GitHub and GitLab. that's it. that's the whole personality 💅 and honestly? obsessed. it does one thing and it ate.

---

🎀 OPTIONS 🎀

• -v, --verbose — use verbose output ✨. it's the flags-with-dots situation: you can pass it more than once, because the synopsis literally shows -v|--verbose with ... after it. so chatty. love that for you.
• -c, --config=PATH — the configuration file 🌈. default is ~/.config/hanko/config.toml (yes, that's the default, yes, it's pretty). may also be specified with the HANKO_CONFIG environment variable 👀
• --file=PATH — the allowed signers file 🎯. may also be specified with the HANKO_ALLOWED_SIGNERS environment variable. two ways to say the same thing, and honestly? valid.
• -h, --help — print help 🫶. the "help me help you" button. press it, it's free.

---

👑 SUBCOMMANDS 👑

• hanko-update(1) — update the allowed signers file 🔥 the main character subcommand fr fr.
• hanko-signer(1) — manage allowed signers 🧚 the sidekick that's honestly also main character energy.

(iykyk — each of those has its own manual page, so go read those next 💜)

---

heads up bestie: -c/--config and --file each have an environment variable twin (HANKO_CONFIG and HANKO_ALLOWED_SIGNERS). the manual doesn't say who wins if you set both, so I'm not gonna invent an answer — no guessing, that's the rule 🌸

---

so yeah, that's hanko(1) in full, nothing skipped, nothing summarised, every flag accounted for ⭐ and yeah — this whole thing lives in the hanko manual, and the date field on the footer is literally empty, so like... timeless? undated? we don't know, and honestly the vibe is immaculate either way 💖🎀🦋