HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
agentstation
uuidkey
Go2025–2025
agentstation / uuidkey

uuidkey

The uuidkey package encodes UUIDs to a readable Key format via the Base32-Crockford codec.

3Distinct people
3Mentions
0Explicit recommenders
199GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The uuidkey package encodes UUIDs to a readable Key format via the Base32-Crockford codec.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM 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 hour3 dated mentions

Observed mentions: 2025-01-10 14:56:26 UTC to 2025-01-11 21:04:29 UTC.

012025-01-10 14:00:00 UTC to 2025-01-10 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 10, 14:002025-01-10 15:00:00 UTC to 2025-01-10 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-10 16:00:00 UTC to 2025-01-10 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-10 17:00:00 UTC to 2025-01-10 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-10 18:00:00 UTC to 2025-01-10 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-10 19:00:00 UTC to 2025-01-10 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-10 20:00:00 UTC to 2025-01-10 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-10 21:00:00 UTC to 2025-01-10 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-10 22:00:00 UTC to 2025-01-10 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-10 23:00:00 UTC to 2025-01-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 00:00:00 UTC to 2025-01-11 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 01:00:00 UTC to 2025-01-11 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 02:00:00 UTC to 2025-01-11 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 03:00:00 UTC to 2025-01-11 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 04:00:00 UTC to 2025-01-11 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 05:00:00 UTC to 2025-01-11 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 11, 05:002025-01-11 06:00:00 UTC to 2025-01-11 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 07:00:00 UTC to 2025-01-11 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 08:00:00 UTC to 2025-01-11 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 09:00:00 UTC to 2025-01-11 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 10:00:00 UTC to 2025-01-11 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 11:00:00 UTC to 2025-01-11 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 12:00:00 UTC to 2025-01-11 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 13:00:00 UTC to 2025-01-11 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 14:00:00 UTC to 2025-01-11 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 15:00:00 UTC to 2025-01-11 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 16:00:00 UTC to 2025-01-11 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 17:00:00 UTC to 2025-01-11 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 18:00:00 UTC to 2025-01-11 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 19:00:00 UTC to 2025-01-11 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 20:00:00 UTC to 2025-01-11 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-11 21:00:00 UTC to 2025-01-11 22:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 11, 21:00

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
Jan 10, 14:002025-01-10 14:00:00 UTC2025-01-10 15:00:00 UTC101
Jan 10, 15:002025-01-10 15:00:00 UTC2025-01-10 16:00:00 UTC101
Jan 10, 16:002025-01-10 16:00:00 UTC2025-01-10 17:00:00 UTC000
Jan 10, 17:002025-01-10 17:00:00 UTC2025-01-10 18:00:00 UTC000
Jan 10, 18:002025-01-10 18:00:00 UTC2025-01-10 19:00:00 UTC000
Jan 10, 19:002025-01-10 19:00:00 UTC2025-01-10 20:00:00 UTC000
Jan 10, 20:002025-01-10 20:00:00 UTC2025-01-10 21:00:00 UTC000
Jan 10, 21:002025-01-10 21:00:00 UTC2025-01-10 22:00:00 UTC000
Jan 10, 22:002025-01-10 22:00:00 UTC2025-01-10 23:00:00 UTC000
Jan 10, 23:002025-01-10 23:00:00 UTC2025-01-11 00:00:00 UTC000
Jan 11, 00:002025-01-11 00:00:00 UTC2025-01-11 01:00:00 UTC000
Jan 11, 01:002025-01-11 01:00:00 UTC2025-01-11 02:00:00 UTC000
Jan 11, 02:002025-01-11 02:00:00 UTC2025-01-11 03:00:00 UTC000
Jan 11, 03:002025-01-11 03:00:00 UTC2025-01-11 04:00:00 UTC000
Jan 11, 04:002025-01-11 04:00:00 UTC2025-01-11 05:00:00 UTC000
Jan 11, 05:002025-01-11 05:00:00 UTC2025-01-11 06:00:00 UTC000
Jan 11, 06:002025-01-11 06:00:00 UTC2025-01-11 07:00:00 UTC000
Jan 11, 07:002025-01-11 07:00:00 UTC2025-01-11 08:00:00 UTC000
Jan 11, 08:002025-01-11 08:00:00 UTC2025-01-11 09:00:00 UTC000
Jan 11, 09:002025-01-11 09:00:00 UTC2025-01-11 10:00:00 UTC000
Jan 11, 10:002025-01-11 10:00:00 UTC2025-01-11 11:00:00 UTC000
Jan 11, 11:002025-01-11 11:00:00 UTC2025-01-11 12:00:00 UTC000
Jan 11, 12:002025-01-11 12:00:00 UTC2025-01-11 13:00:00 UTC000
Jan 11, 13:002025-01-11 13:00:00 UTC2025-01-11 14:00:00 UTC000
Jan 11, 14:002025-01-11 14:00:00 UTC2025-01-11 15:00:00 UTC000
Jan 11, 15:002025-01-11 15:00:00 UTC2025-01-11 16:00:00 UTC000
Jan 11, 16:002025-01-11 16:00:00 UTC2025-01-11 17:00:00 UTC000
Jan 11, 17:002025-01-11 17:00:00 UTC2025-01-11 18:00:00 UTC000
Jan 11, 18:002025-01-11 18:00:00 UTC2025-01-11 19:00:00 UTC000
Jan 11, 19:002025-01-11 19:00:00 UTC2025-01-11 20:00:00 UTC000
Jan 11, 20:002025-01-11 20:00:00 UTC2025-01-11 21:00:00 UTC000
Jan 11, 21:002025-01-11 21:00:00 UTC2025-01-11 22:00:00 UTC101

What Hacker News says

3 sources
Hey everyone. Thanks for all the discussion on the article. We wanted to respond to a few common themes: 0. Some folks don't care about API Keys, that's okay! But for those of you who did respond and do care, we are updating our design based on your feedback. 1. When we got to work on making our API Keys, we looked for an obvious standard but didn't find one. So we decided on our approach quickly and put together uuidkey in an afternoon. We knew it was not going to be everyone’s preferred design, but we wrote up the article to share our thought process as well as generate some marketing. We are happy to see that the article did well and we got feedback! :) 2. The ability to double-click to copy, which was lost with the addition of dashes, was more important to developer commenters than we thought it'd be (even if only needed once). We
Read the rest
heard you, so we've already updated https://github.com/agentstation/uuidkey to support a `WithoutHyphens` option for the `Encode` function so you can generate keys without dashes. 3. Some folks were worried that our resulting key after encoding has fewer bits of entropy compared to the original UUID. The Crockford base32 encoding does not reduce entropy, it is a 1:1 mapping. 4. One quality piece of feedback pointed out that the UUID spec warns against using UUIDv7 (only 74 bits of entropy) and even UUIDv4 (standard 122 bits of entropy) alone for API Keys. We plan on still supporting UUIDv7 and UUIDv4, but will add additional entropy bits to follow the official recommendation. 4. Lots of commenters like prefixes, which make it easier to identify & search for keys (particularly to ensure they don’t get accidentally committed to a repo). We plan to add an option for that. Worth mentioning that a few folks pointed us to Github's auth token implementation that includes prefixes, which is a pretty great standard - https://github.blog/engineering/platform-security/behind-git... Thanks again for reading, debating, and giving us some good advice! We want a product that feels good for developers to use. :D
In Making Beautiful API Keys
I don't think so since the sample key they present in the big image contains many of these. The caption is "An example API key generated by github.com/gofrs/uuid and encoded with github.com/agentstation/uuidkey." - so something is wrong.
In Making Beautiful API Keys

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.