Ever wanted to be supported in a sustainable way for the amazing packages that you created? We help you do just that.
Publishing either new packages or new versions of existing packages, it's as easy as npm publish
.
In addition, the OpenSource registry functions as a drop-in registry replacement minimizing the impact on companies and users of your packages.
Read details about funds share calculation here.
Signup and start getting your fund share as of today!
Join us on Discord to discuss the latest updates, share your thoughts on new features, or just chat with like-minded individuals.
We'd love to stay connected with you. If you'd like to be notified of new features, updates, and more, follow @ossregistry on Twitter.
Whether you're a seasoned developer or just starting out, our subreddit is the perfect platform to showcase your work
Maintaining opensource is just work, many developers lose interest at some point without proper support. Our support model lets the opensource developers focus on the things they love and care.
We value opensource developers as musicians and see companies as the listeners. Like various music platforms, you get all the best opensource for a fixed monthly fee.
We take a small 6% fee from your provided funds to keep the registry running. Your funds are really spent on the developers, which in part make your business run!
Did you know all commercial software products/web-services consist of opensource software for more than half the codebase? Ask your in-house developers for details.
Free forever, this plan allows individual users to use OpenSource Registry non-commercially.
$0 /mo forever
Get startedUse OpenSource Registry commercially for any and all products/services.
$200 /mo
Start with CommercialSign up for our newsletter to stay up to date.
We care about the protection of your data. Read our Privacy Policy.
Installing packages from/via the OpenSource Registry is very simple. Just open a terminal and change your registry using the commands below. The auth-token required for the second command was sent to your email address after signup but can also be retrieved from the dashboard
npm set registry https://npm.opensourceregistry.com
npm set //npm.opensourceregistry.com/:_authToken <provided-token>
You should now be able to use NPM using the OpenSource Registry. If you run into any trouble, feel free to message us at our support email
Before publishing the first version create a package entry in the my packages page.
Add the following line to your package.json file to the project you want to publish:
"publishConfig": { "registry": "https://npm-publish.opensourceregistry.com" }
Then type the following:
npm set //npm-publish.opensourceregistry.com/:_authToken <provided-token>
Do the actual publish:
npm publish
See the docs for more info.
We take your package download count divided by the total download count, multiplied by the total available funds.
This is saying you will get the relative share of all funding money based on your download count in relation to all downloads.
Note: Any counts used are unique IP address counts. A company build server doing many downloads a day/month will be seen as one count.