Add cryptographically secure NanoID/UUID generator

[mprimeaux]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/sixafter/nanoid
• pkg.go.dev: https://pkg.go.dev/github.com/sixafter/nanoid
• goreportcard.com: https://goreportcard.com/report/github.com/sixafter/nanoid
• coverage service link (codecov, coveralls, etc.): https://sonarcloud.io/summary/new_code?id=six-after_nano-id

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

• I removed the following packages around my addition:
  • https://github.com/telesvar/nanoid as the implementation is now a public archive and therefore no longer maintained. The last commit as of this PR was 4 years ago.

Though Sno has not had a commit in 4 years but has not been archived, I decided against removing it as is unique in this category.

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Updated the UUID library reference: replaced the previous NanoID entry with a different implementation and revised the description to highlight more secure, concurrent NanoID/UUID generation.

_{��️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated README.md to replace the nanoid reference from aidarkhanov/nanoid to sixafter/nanoid and broadened the description to emphasize cryptographic security and concurrent NanoID/UUID generation.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Replaced nanoid repository reference from aidarkhanov/nanoid to sixafter/nanoid; reworded and expanded description to highlight cryptographic security, speed, and concurrent generation capabilities; minor punctuation edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Documentation-only change; no code modifications
• Single file to verify (README.md)

Poem

🐇 I nibble lines and tweak a name,
A tiny change, but not for fame.
Secure small seeds now wheel and spin,
Fast little IDs hop softly in. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add cryptographically secure NanoID/UUID generator' directly matches the PR's main change: replacing the nanoid entry with a more secure implementation from sixafter/nanoid in the README.md.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0ca1472 and e3baeb7.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: quality

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: OK
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: missing

These checks are a best-effort automation and do not replace human review.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

2946-2946: Verification passed; optional copy neutralization suggested.

The repo migration is clean and verified:

• No stale references to the old repo found in README.md
• New repo and pkg.go.dev docs are accessible (HTTP 200)

The change follows list rules: maintains alphabetical order, category has multiple entries, description ends with a period.

To improve alignment with the "concise and neutral" guideline, consider this minimal copy adjustment:

-- [nanoid](https://github.com/sixafter/nanoid) - A tiny, efficient, cryptographically secure generator for fast, concurrent NanoID and UUID creation.
+- [nanoid](https://github.com/sixafter/nanoid) - Cryptographically secure NanoID and UUID generator with concurrent creation support.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2698e59 and 0ca1472.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

README.md

📄 CodeRabbit inference engine (AGENTS.md)

README.md: When modifying the Awesome list, keep categories with at least three entries
Descriptions in the Awesome list must end with a period
Avoid promotional copy; keep descriptions concise and neutral in the Awesome list
Do not remove existing list content unless removal is requested and justified

Files:

• README.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• README.md

{README.md,COVERAGE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Align rendered documentation (README.md, COVERAGE.md, etc.) with behavior changes in main.go or helper packages

Files:

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

[mprimeaux]

Though a bit challenging to see, the coverage is at 91%. Please see SonarCloud and select the "Overall Code" tab as per the attached.

[mprimeaux]

Hi @avelino. Please let me know if I can adjust anything. Happy to do so.

[mprimeaux]

@avelino Please let me know if I can provide any other detail. Thanks for your continued help and support.