spew VS ulid

github.com/davecgh/go-spew

go-spew - god sent for debugging

go-spew : Really helpful to pretty print user defined data structures, makes debugging a lot easier.

There is no "tests".

There is just a single test. Which only tests the decoding of a single known value. No encoding test.

Go has infrastructure for benchmarking and fuzzing. Use it!

Also, you took code from https://github.com/oklog/ulid/blob/main/ulid.go which has "Copyright 2016 The Oklog Authors" but this is not mentionned in your base32.go.

maybe because of dependencies: https://github.com/oklog/ulid/blob/main/go.mod ??

You can also have look at https://github.com/oklog/ulid for time ordering generated id purpose

Universally Unique Lexicographically Sortable Identifier

I'm not concerned too much about the performance or the storage size at this stage. I've checked ulids before posting (more specifically https://github.com/oklog/ulid) but the only difference than a random string (especially if you use them with math.rand) is the timestamp prefix which makes them sortable, but I don't need that (users could use the internal SQLite rowid if they needed to sort by a primary key).

why are you using https://github.com/oklog/ulid to generate a cookie secret?

oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).