That information is now available in the new X-RateLimit-Reset response header.
$ curl -I https://api.github.com/orgs/octokit

HTTP/1.1 200 OK
Status: 200 OK
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 42
X-RateLimit-Reset: 1372700873
...
The X-RateLimit-Reset header provides a Unix UTC timestamp, letting you know the exact time that your fresh new rate limit kicks in.

The reset timestamp is also available as part of the /rate_limit resource.
$ curl https://api.github.com/rate_limit

{
"rate": {
"limit": 60,
"remaining": 42,
"reset": 1372700873
}
}

Everything I looked at seems to be rated pretty well. Suggest perhaps making it harder to get > 4 stars.

Also:
Not clear exactly how metrics are measured. Suggest some brief description as hover tooltip.
Not clear what an author can do to improve quality. "Is this your package? Here's what you can do to improve your score."

Leave pending tasks when several pages of issues are found. Write a getIssuesForRepo(name, from, to, callback) for this purpose. Proccess each chuck, and then go for the peding issues. This way we get better control of the remaining API calls to github.

In the new "unify" version, the registry (http://registry.npmjs.org/) is called twice, once for checking that the package exists, and another one to estimate the versions factor. Caching this request for 20 seconds will save us a call.

The bit "npm" in "Package from npm" in the page for loadtest should take the user to the npm page: https://www.npmjs.com/package/loadtest.

Hi all.

I love this idea, how clean and minimalist it is.

I do worry about how new packages are treated by the calculations. In the very beginning of a package's life it can't (or shouldn't) be treated as a low quality package.

For the sake of clarity, let's assume a package has just been published. No matter how good or well coded it is, it will be a zero-star package assuming most of its considered stats are in zero:

DOWNLOADS = 0;
VERSIONS = 1;
TOTAL_ISSUES = 0; //maybe the package is SO good it doesn't have any issues (just maybe)
OPEN_ISSUES = 0; //idem above
LONG_ISSUES = 0; //because above

v = 1 - 1 / VERSIONS;
// 1 / 1 = 1; 1 - 1 = 0; zero rating so far
d = 1 - 1 / DOWNLOADS;
// 1 / 0 = error; 1 - error = ?; zero rating remains

rt = 1 - 1 / TOTAL_ISSUES;
// 1 / 0 = error; 1 - error = ?; zero rating remains
ro = 1 - 1 / OPEN_ISSUES;
// 1 / 0 = error; 1 - error = ?; zero rating remains
rlo = 1 - 1 / LONG_ISSUES;
// 1 / 0 = error; 1 - error = ?; zero rating remains
r = (rt + ro + rlo) / 3; //zero again

So, how does a package relates to its quality by this calculations? Well, it doesn't.

Quality shouldn't be confused with popularity or maintained package. This stats are only checking for "how much" (a quantitative measure) and not for "how good" (qualitative).

I think a harder work has to be applied to the ratings and how are they calculated. Things like downloads shouldn't be taken on quality measures unless we can find a relation with other packages depending on the one being measured. Documentation is, by far, one of the most important things in a package quality (besides code itself) and is not even mentioned here.

Let's face it, even if someone wrote the perfect package, it would receive zero star rating because it doesn't have any downloads, or because it doesn't have any issues. A package could be perfect (not often) and not need any issues, yet it would still receive a zero star rating.

I'd love to see this tool go further into a deep analysis of the package and post a, relatively, improved version of the ratings.

My package is registered on NPM but it does not find it (doesn't matter) but if there's an error (e.g. not found), the code should not be displayed with "undefined" & co. 😃 thanks!

Add a retina ready quality banner. Now the banner looks like a s**t on retina display :)

my gh badge:

quality report: http://packagequality.com/#?package=koa-verto

badge in npm package page is ok

Take a look at measurements for clusterize.js package
Shield's and badge's stars vary

I suspect it's because badge fetch clusterize package instead of clusterize.js

The results for geometric and harmonic averages are not acceptable: they violate the universal values for star ratings since most packages have zero (and not 1~3). We should use an arithmetic average, with the same weights as now, and start with one star.

Taken from https://skimdb.npmjs.com/, as recommended by @isaacs.

Packages that are scoped (Use @) break the image URL:
http://npm.packagequality.com/#?package=@google%2Fclasp

Is there a way to submit new packages?

This one is missing: http://packagequality.com/#?package=copee

Here it is in npm: https://www.npmjs.com/package/copee

So we can draw time charts

It would be great to have badges that show package quality for a repo, using a simple URL scheme. They can then be added to package READMEs.

The page for the dna.js project shows metadata from the dna-js project.

The tag line for:
http://packagequality.com/#?package=dna.js
displays:
Human friendly data format.

It should display:
An uncomplicated user interface library for semantic templates
as can be seen on the dna.js npm page:
https://www.npmjs.com/package/dna.js

Note that the tag line for:
http://packagequality.com/#?package=dna-js
correctly displays:
Human friendly data format.

Snippet is wrong: http://npm.packagequality.com/#?package=testing shows badge for http://packagequality.com/badge/undefined.png.

Otherwise the log files will end up dominating the world.

Since we have the vocation of being a universal package quality indicator, we should prefix all URLs with /npm/ so that other package managers can reside in /maven/, /pypi/ and so on.

Just out of curiosity I tried with one of my packages, pg-promise

It dropped the rating a lot based on the number of issues that were open over the package's lifespan.

A popular, high-quality package will naturally receive much attention, and much of that attention is in questions and ideas people bring to the table. In my project all questions have been answered and all ideas have been met, no issues open at all, and yet the rating is dropped because there were questions and ideas published on GitHub? This is nonsense. This absolutely does not reflect the package's quality.

Users may need to install "libgif-dev" at operating system level before installing npm dependencies.

This can achieved in debian/ubuntu doing:
sudo apt-get install libgif-dev

And under OSX:
brew install libgif-dev

I will try to update the docs too to include that after the SVG patch.

I would like to look at the "quality" of my package. Unfortunately packagequality.com says it could not find it.

Awesome idea!

I would suggest a simpler badge design in addition to the current one. I know a lot of people use the shields.io style badges in their packages, and putting the current package-quality badge next to them doesn't look very well.

Would also be awesome with the same styles as shields.io:

I know that this project is code agnostic at the moment, but a metric like this actually indicates something about the quality of the code.

The presence of .jslint.conf, .jshintrc or .eslintrc indicates which linter to use, and the results of the linting could inform the rating.

See http://packagequality.com/#?package=package-quality

When I search for any package that is scoped under an org or username I get 404's.

For instance:
@storybook/react

User Statement

As a Package Quality (PQ) user, I would like to see the version of the package I searched for, so that I know what version on npm PQ is looking at.

Details

I know the service currently just looking at the current version on npm but the reassurance is a nice-to-have. I think it could fit well in two places:

• Underneath the star rating, to the right and vertically aligned with "Package from "
• Or replacing the text "Package from" entirley.

Implementation Suggestions

Some formatting options:

• "Version X.X.X from "
• "vX.X.X from"
• "X.X.X from"

Great app! Keep up the good work!

When a package has a GitHub repo but no issues, it shows with quality factors null. It should show which quality factor has actually lowered its score to zero, for improved transparency.

Sample: microprofiler.

{
"_id":"54cad1fd465dcde6761d2b96",
"name":"microprofiler",
"source":"npm",
"repoQuality":0,
"repoFactors":null,
"quality":0,
"created":"2015-02-06T04:27:50+00:00",
"lastUpdated":"2015-02-06T04:27:50+00:00",
"nextUpdate":"2015-03-06T04:27:50+00:00",
"timesUpdated":0
}

http://packagequality.com/#?package=lost

Is package-quality rating an old package or something? lost has been around for a few years as a grid (not as a "cache everything" although I may have got the npm pkg name from someone).

Still though... few years.

that will run every week and refresh the pertinent packages

Create a usage section in the README that details how people can easily run the whole application locally.

Your badge is still served from http.

https://www.i18next.com/ console:

I am getting package not found errors for npm packages that are published and are on Github. Try two of mine: stringformatter and propertyinterceptor.

I'm new to publishing using npm, so perhaps the quality of my publishing is so bad, you can't read them!

For example http://npm.packagequality.com/shield/babel.svg

Hello Alex,
I created an application http://bestof.js.org/ to help developers find the best components of the web platform (front and back end).
Basically it is a curated list of 500 projects on Github about JavaScript in the browser and in node.js, html, css,..
Every day the application checks variations of stars on Github to detect trends.
I would like to display more relevant information about the quality of the projects.
So I wonder if there is a kind of open API to access data generated by http://packagequality.com/ so that I could display the metrics you generate ?
Of course, I would add links to your application and add credits to make obvious the source of the information.
Thank you in advance for your answer and feel free to give me any feedback about bestof.js.org, especially if it is bad feedback ;)

Right now, the repoQuality of those packages with a repository in a place other than github are considered to have zero quality

Open this image: http://packagequality.com/badge/undefined.png. It shows random stars every time you reload the page. It happens with all packages.

This issue seems to be similar to #58

The quality on website is 4 stars, check it here
But the badege appears 2.5 stars on GITHUB

However, the svg image seems correct on an independent browser label

I have cleared my browser cache and cookies, but the problem still exists. I wonder why does it happen? 🤣

Here is my repo vis-ui.

For some obscure reason their repoTotalQuality is "-Infinity" nad for other ever more obscure its harmonic mean is higher than one:

db.packages.findOne({name:"gulp-filter"})
{
"_id" : ObjectId("54e25979f22796cf67c79252"),
"name" : "gulp-filter",
"source" : "npm",
"created" : "2015-02-16T20:56:10+00:00",
"lastUpdated" : "2015-02-17T15:59:01+00:00",
"nextUpdate" : "2015-02-17T15:59:01+00:00",
"timesUpdated" : 1,
"repoTotalIssues" : [
-Infinity,
1
],
"repoOpenIssues" : [
1,
1
],
"repoLongOpenIssues" : [
1,
1
],
"versions" : [
0.9375,
1
],
"downloads" : [
0.9999973556026845,
1
],
"quality" : 1.2295073972177069
}
db.packages.count({quality:{$gt:1.0}})
73
db.packages.findOne({quality:{$gt:1.0}})
{
"_id" : ObjectId("54e23064f22796cf67c75330"),
"name" : "fedtools",
"source" : "npm",
"created" : "2015-02-16T18:00:52+00:00",
"lastUpdated" : "2015-02-17T13:05:47+00:00",
"nextUpdate" : "2015-02-17T13:05:47+00:00",
"timesUpdated" : 1,
"repoTotalIssues" : [
-Infinity,
1
],
"repoOpenIssues" : [
1,
1
],
"repoLongOpenIssues" : [
1,
1
],
"versions" : [
0.995049504950495,
1
],
"downloads" : [
0.9999830203416308,
1
],
"quality" : 1.2484419119330468
}

Interesting project 👍 . Having something like this would be hanging when deciding if a dependency is worth being added or removed.

Well, let's not start sucking each other's dicks quite yet. Badges shows a weird text.

Tested with Firefox 41 and Chrome 45 under Ubuntu 14.04.

Looking the code, it seems like you try to place the ASCII (filled or unfilled) stars in SVG but it's not well encoded at server side or decoded at client one. The "one half" character have no issues.

I'll try to help with it if I've time and nobody solves it before.

We should have a page that displays top 100 packages.

Currently there are two versions of the site:

• mongo uses MongoDB to read package information,
• no_mongo queries GitHub and other datasources concurrently and gets an answer, so the package is checked online.

It would be great to have a single, unified version that uses cached information, and if it's outdated checks online.

In addition to the date, package information might contain a version field checked by the server: if earlier than a given version it is considered outdated and checked online.

Example: @author/packagename

This will provide a hint to the updater to what packages should be refreshed and which shouldn't

So that the domain packagequality.com can run on port 80.

I have a package jquery.terminal but when I search I only get bioship.jquery.terminal. the package can be found by changing the url to http://packagequality.com/#?package=jquery.terminal