A look at nim-lang/packages: 503 stars on GitHub, written primarily in Nim. List of packages for Nimble
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This is a central listing of all packages for
Nimble, a package manager for the
Nim programming language.
An overview of all packages is available at https://nimble.directory or https://nimpkgs.org.
NOTE: The packages listed here are not peer-reviewed or otherwise screened. We try to keep the list up-to-date but we cannot guarantee quality or maturity of the packages.
Adding your own package
To add your own package, fork this repository, edit
packages.json and make a pull request.
Packages.json is a simple array of objects. Each package
object should have the following fields (unless the field is marked as
optional):
name - The name of the package, this should match the name in the package's
nimble file.
url - The url from which to retrieve the package.
method - The method that should be used to retrieve this package. Currently
"git" and "hg" is supported.
tags - A list of tags describing this package.
description - A description of this package.
license - The license of the source code in the package.
web - An optional URL for humans to read additional information about
the package.
doc - An optional URL for humans to read the package HTML documentation
Requirements
While we really appreciate your contribution, please follow the requirements: other developers will rely on your package. Non-compliant packages might be removed with no warning.
The URL should work, a .nimble file should be present and the package should be installable
The package should build correctly with the latest Nim release
The package should not contain files without a license or in breach of 3rd parties licensing
Non-mature packages should be flagged as such by opening an issue here with a good explanation on how they are non-mature, especially if they perform security-critical tasks (e.g. encryption)
If a vulnerability is found, make a patch release against the latest stable release (or more) that fixes the issue without introducing any other change.
Tiny libraries should be avoided where possible
Avoid having many dependencies. Use "when defined(...)" to enable optional features.
If abandoning a package, please tag it as "abandoned"
The package name should be unique and specific. Avoid overly generic names e.g. "math", "http"
Provide a contact email address.
Optionally try to support older Nim releases (6 months to 1 year)
Optionally GPG-sign your releases
Optionally follow SemVer 2
Your packages may be removed if the url stops working. It goes without saying
that your pull request will not be accepted unless you fill out all of the
above required fields correctly, the package that url points to must also
contain a .nimble file, or else it will be rejected.
The requirements might change in future.
Releasing a new package version
The version number in the directory is derived from git tags (not the version field in the .nimble script). To release a new version of a package, follow the instructions from the Nimble readme:
Increment the version in your .nimble file.
Commit your changes.
Tag your release, by for example running git tag v0.2.0.
Push your tags and commits.
Renaming packages
To rename a package you will need to add a new entry for your package. Simply
perform the following steps:
Duplicate your package's current entry.
Remove every field in one of the entries apart from the name field.
The most recent commit recorded on nim-lang/packages was 11 days ago, based on the GitHub push timestamp. The repository has 805 forks — one of the better signals of community interest.
How many stars does nim-lang/packages have?
nim-lang/packages has 503 GitHub stars — refresh the page for the live number, or check github.com/nim-lang/packages. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is nim-lang/packages written in?
nim-lang/packages is written primarily in Nim. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is nim-lang/packages associated with?
GitHub's repository topics for nim-lang/packages: "nim", "nimble", "packages". TopGit's editorial category is open-source.
Where do I read more about nim-lang/packages?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/nim-lang/packages is the definitive source.
Read full README in the tab above.
Is packages worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of packages.