Contribution Guidelines

Adding to this list

Please ensure your pull request adheres to the following guidelines:

• Make an individual pull request for each suggestion.
• Use the following format: [Resource Name](link) - Short description.
• Don't repeat the resource name in the description.
• Link additions should be added in alphabetical order to the relevant category.
• Titles should be capitalized.
• Check your spelling and grammar.
• New categories or improvements to the existing categorization are welcome.
• The pull request and commit should have a useful title.

Quality criteria for project and library entries

To keep this list curated rather than exhaustive, entries that point to a project or library repository should be well-known and actively maintained. As a rule of thumb:

• The project should have at least 30 GitHub stars (or equivalent traction on its platform).
• The repository should be actively maintained — not archived or abandoned.
• The project should be well documented — a clear README, usage examples, and setup instructions so others can actually adopt it.
• Prefer one canonical entry per language/ecosystem over many near-duplicate ports of the same tool.
• Avoid self-promotion. Submissions should benefit the community, not primarily advertise your own project; if you are the author, please disclose it in the pull request.

Star count is a guideline, not a hard gate — a low-star project may still be accepted if it is the shared protocol or dependency that already-listed projects build on. Reference material (RFCs, specs, articles, talks) is exempt from the star criterion.

Thank you for your suggestions!