Hi @scippie I would suggest that you go with the personal repo and potentially the package-version in your repo for production projects:
1. Cloning the repo to ensure that you can manage all changes. Then simply `pull` and `git fetch --tags upstream && git push --tags` to keep it up to date. 2. Using the `nimbledeps` directory in your projects to keep the dependencies within the projects repo and commit them. I had some trouble with `nimbledeps` due to working with Nim v1.6.18 and v2. That was solved by setting the nimblePath in the `config.nims`: when NimMajor >= 2: switch("nimblePath", "nimbledeps/pkgs2") else: switch("nimblePath", "nimbledeps/pkgs") Run To activate the `nimbledeps` just: $ mkdir nimbledeps $ nimble install <package name> Run