Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


List of packages for Nimble

Subscribe to updates I use packages

Statistics on packages

Number of watchers on Github 117
Number of open issues 4
Average time to close an issue about 1 hour
Main language Nimrod
Average time to merge a PR about 18 hours
Open pull requests 14+
Closed pull requests 46+
Last commit about 2 years ago
Repo Created over 7 years ago
Repo Last Updated about 2 years ago
Size 1.49 MB
Organization / Authornim-lang
Page Updated
Do you use packages? Leave a review!
View open issues (4)
View packages activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating packages for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

Nim packages Build Status

This is a central listing of all packages for Nimble, a package manager for the Nim programming language.

An overview of all Nimble packages is available in the library documentation.

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


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, especially if they perform security-critical tasks (e.g. encryption)
  • If abandoning a package, please tag it as abandoned
  • Optionally GPG-sign your releases
  • Optionally follow SemVer

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.

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.
  • Add an alias field to that entry.
  • Change the name in the other package entry.

For example:

    "name": "myoldname",
    "alias": "mynewname"
    "name": "mynewname",
    "url": "...",
    "method": "git",
packages open issues Ask a question     (View All Issues)
  • over 3 years Tag naming / checking
  • almost 4 years Package name scheme
packages open pull requests (View All Pulls)
  • Added package nimyaml
  • Add package sam
  • Add more requirements to the package list
  • Add classifiers
  • Add i18n module
  • Added aws_sdk
  • Added nimzend package.
  • Add package mmgeoip
  • removed dash from the libtcod package name
  • add polyBool package
  • Added odbc library
  • Add CLBlast, a wrapper for the OpenCL BLAS library
  • Register ttmath
  • nim_exodus
packages questions on Stackoverflow (View All Questions)
  • Node js - cant install packages on a server
  • How to list npm user-installed packages?
  • Nuget copy file from packages folder to project directory
  • what is the use of public/packages directory in laravel 4
  • What are the OOD principles for Java namespace packages?
  • Why would Visual Studio give access denied, code 5 error when trying to build solution with NuGet packages?
  • Meteor packages for ranking/voting/scoring
  • How to organize Go code in packages
  • Saltstack Packages Failed to Install on OpenBSD 5.8
  • Dynamically Generate file connection for several packages in SSIS
  • pycurl version conflict between installed packages
  • How to load npm packages with ClosureCompiler.js
  • Implicit vs. unnamed packages
  • (closed) Python: No module named cv2, unless first cd ~/.virtualenvs/cv/lib/python2.7/site-packages/
  • Error Importing Python Packages into Jupyter
  • tell pip to install the dependencies of packages listed in a requirement file
  • pip (1.3.1) not upgrading packages until the local cache is deleted
  • TFS: remove packages folder that was already committed
  • Can't install any packages in Node.js using "npm install"
  • Could not remove destination file /usr/share/mime/packages/: Unknown error
  • using Authorization laravel in packages
  • Nonlinear system of equation in R packages
  • Any smart JSON/JS Object counting packages?
  • Remove Stack/Cabal packages and install older versions
  • How create multi packages on one Library project "android studio" (JAVA)?
  • Python: pip installs sub-packages in root dir
  • django - looking for libaries/packages for chat application
  • Xamarin Forms Android Error Message Regarding Support Package and other packages
  • Ambiguity between packages in MVC project
  • What do the *-dev packages in the Linux package repositories actually contain?
packages list of languages used
Other projects in Nimrod