Live data from Hacker News

Which NPM package has the largest version number?

adamhl.dev

21–30 of 80 posts

Re: Which NPM package has the largest version number?

#21

The "winner" just had its 3000th release on GitHub, already a few patch versions past the version referenced in this article (which was published today): https://github.com/wppconnect-team/wa-version

After double-checking some things, the real winner is actually: https://github.com/nice-registry/all-the-package-names

I made a fairly significant (dumb) mistake in the logic for extracting valid semver versions. I was doing a falsy check, so if any of major/minor/patch in the version was a 0, the whole package was ignored.

The post has been updated to reflect this.

Re: Which NPM package has the largest version number?

#23
post #14

Earlier quoted context omitted.

Maybe that is intentional? Which package is it?

It's the type definitions for developing chrome extensions. They'd been incrementing in the 0.0.x lane for almost a decade and bumped it to 0.1.0 after I raised the issue, so I doubt it was intentional: https://www.npmjs.com/package/@types/chrome?activeTab=versio...

This is part of the DefinitelyTyped project. DT tends to get a lot of one-off contributions just for fixing the one error a dev is experiencing. So maybe they all just copied the version incrementing that previous commits had done, and no one in particular ever took the responsibility to say "this is ready now".

Re: Which NPM package has the largest version number?

#24

One of the 'winners' I randomly googled. > carrot-scan -> 27708 total versions > Command-line tool for detecting vulnerabilities in files and directories. I can't help but feel there is something absurd about this.

Each version is likely a new vulnerability that got submitted, doesn't seem that weird.

Re: Which NPM package has the largest version number?

#25
Haha, good luck finding a real project that holds that title. It's always some squatted name, a dependency confusion experiment, or a troll publishing a package with version 99999.99999.99999 just to see what breaks. The "king" of that hill changes all the time. Just another day in the NPM circus.

Re: Which NPM package has the largest version number?

#27
post #24

One of the 'winners' I randomly googled. > carrot-scan -> 27708 total versions > Command-line tool for detecting vulnerabilities in files and directories. I can't help but feel there is something absurd about this.

Each version is likely a new vulnerability that got submitted, doesn't seem that weird.

Shouldn't vulnerabilities be "data" in this context? You bump the vulns database but keep the code at the same version if the logic is the same.

Re: Which NPM package has the largest version number?

#28

Incidentally I once ran into a mature package that had lived in the 0.0.x lane forever and treated every release as a patch, racking up a huge version number, and I had to remind the maintainer that users depending with caret ranges won't get those updates automatically. (In semver caret ranges never change the leftmost non-zero digit; in 0.0.x that digit is the patch version, so ^0.0.123 is just a hard pin to 0.0.12…

Presumably they’re following https://0ver.org/

Re: Which NPM package has the largest version number?

#29

For Python (or PyPI) this is easier, since their data is available on Google BigQuery [1], so you can just run SELECT * FROM `bigquery-public-data.pypi.distribution_metadata` ORDER BY length(version) DESC LIMIT 10 The winner is: https://pypi.org/project/elvisgogo/#history The package with most versions still listed on PyPI is spanishconjugator [2], which consistently published ~240 releases per month between 2020 and…

You can also query for free at clickpy.clickhouse.com. If you click on any of the links on the visuals you can see the query used.

The underlying dataset is hosted at sql.clickhouse.com e.g. https://sql.clickhouse.com/?query=U0VMRUNUIGNvdW50KCkgICBGUk...

disclaimer: built this a a while ago but we maintain this at clickhouse

oh and rubygems data is also there.

Re: Which NPM package has the largest version number?

#30

Anthony Fu’s epoch versioning scheme (to differentiate breaking change majors from "marketing" majors) could yield easy winners here, at least on the raw version number alone (not the number of sequential versions released): https://antfu.me/posts/epoch-semver

> People often assume that a zero-major version indicates that the software is not ready for production

I wonder why. Conventions that are being broken, maybe.

Post reply on HN