Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time
April 19, 2019 19:22
November 24, 2021 17:15
November 11, 2015 17:28
April 18, 2023 16:57
November 24, 2021 17:15
April 18, 2023 16:57
May 11, 2020 17:02
December 15, 2022 19:06
November 16, 2023 18:19


QLNet C# library official repository. QLNet is a financial library written in C# derived primarily from its C++ counterpart, Quantlib, which has been used as a base reference for modelling various financial instruments. QLNet also contains new developments on the bond market like MBS, Amortized Cost, PSA Curve and others.

Build status NuGet Donate

Quality Gate Status Bugs Vulnerabilities Code Smells Duplicated Lines (%) Lines of Code Maintainability Rating Reliability Rating Security Rating Technical Debt

Development workflow

QLNet use git flow workflow.

Instead of a single master branch, this workflow uses two branches to record the history of the project. The master branch stores the official release history, and the develop branch serves as an integration branch for features. The develop branch will also contain the complete history of the project.


To contribute features, you should clone the repository, create a tracking branch for develop and create the feature:

git clone
git checkout -b develop origin/develop
git checkout -b some-feature develop

When the feature is ready, you can make a pull request to merge that feature into develop. Note that features will never be merged directly into master.


When a release is ready, we fork a release branch from develop. Creating this branch starts the next release cycle, so no new features can be added after this point; only bug fixes, documentation generation, and other release-oriented tasks go in this branch. Once it's ready to ship, the release gets merged into master and tagged with a version number.


Maintenance or “hotfix” branches are used to quickly patch production releases. This is the only branch that fork directly off of master. As soon as the fix is complete, it will be merged into both master and develop, and master will be tagged with an updated version number.


Thanks to all Quantlib creators and contributors. Thanks to all QLNet contributors. Special thanks to JetBrains for their support of open source projects; QLNet makes extensive use of Resharper.