npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

oscalc

v1.1.0

Published

[Open calculator](https://elecash.github.io/os-calculator/)

Downloads

9

Readme

How much are you saving with the Open Source projects you're using?

Open calculator

How do you calculate the value?

We use the excellent npms.io API to get a metric about how well maintained is the repository, its code quality and popularity. Then we sum all stars in the repositories you're using and multiply these by npms.io metric. Finally we calculate that for every 100 stars a maintainer spends 1 hour per week on the project.

For example: (number of stars️ x npms.io metric / 100) x price hour

Is it accurate?

Hell, no!

I'm pretty sure that the total value is way higher than we think.

Why is this interesting?

Every day private companies are trusting more and more in Open Source projects that are not properly maintained due to a lack of financial support. Problems like left-pad, event-stream or 1337qq-js are just the tip of the iceberg.

Is not sponsoring enough?

Sponsors are peanuts.

If you pay peanuts, you get monkeys.

But Open Source projects can create Licenses to get paid

Licensing models work pretty well for big Open Source projects that are usually behind a company.

There are thousands of small Open Source projects that are being used and nobody knows that they're using it. Still, the developers behind those libraries have to maintain a fragile ecosystem for free and private companies are in risk that those libraries stop being maintained, transferred ownership to potential hackers or worst.

What do you suggest?

I do not have a correct answer here. Maybe a royalty system might be a good idea, but the music industry royalty system has been a failure.

Are you suggesting that we all should pay for using Open Source projects?

NO.

I think that companies obtaining an economic benefit by using heavily Open Source projects should compensate economically those projects.

Being paid is not against Open Source?

No. There are a lot of Open Source projects that have enterprise models to get a return.

Why are you doing this?

I love Open Source. I've created and contributed to Open Source projects for the last 13 years, and I'll keep doing it. I'm just worried about its future.

I have a question, how can I contact you?

You can create an issue on this repository.