Huge package

I happened to see this package as I was looking for a state machine implementation. You may notice the NPM reports bundle sizes now, and yours is 25mb. I actually downloaded the package tarball just to see if I should report it as a virus.

Here are things you are currently shipping that you might not want to be:

/.rp2t_cache/**
/docs/**
/src/**
/.github/**
/notes/**
.nycrc
.eslintrc
.editorconfig

Of course, much easier would be to set the package files field to just be /dist/**

[StoneCypher]

oh holy crap. thank you for letting me know

[StoneCypher]

It’s well known that the number of issues and their age is a factor in the old npms.io algorithm. That’s why I transitioned all my issues to a different repo.

You can see it in the api response for a different repo (warning, large unformatted json). I use the fsl repo for the example instead of the jssm repo because since the jssm repo now has no relevant issues, the section is removed.

The two relevant pieces are the maintenance section and the github breakdown:

    "evaluation":{
        "quality":{
            "carefulness":0.192075,
            "tests":0,
            "health":1,
            "branding":0
        },
        "popularity":{
            "communityInterest":9,
            "downloadsCount":8.333333333333334,
            "downloadsAcceleration":-0.03247716894977169,
            "dependentsCount":0
        },
        "maintenance":{
            "releasesFrequency":0,
            "commitsFrequency":0.011506849315068493,
            "openIssues":0.1772908366533864,
            "issuesDistribution":0
        }
    },

and

        "github":{
            "starsCount":5,
            "forksCount":1,
            "subscribersCount":2,
            "issues":{
                "count":502,
                "openCount":413,
                "distribution":{
                    "3600":24,
                    "10800":11,
                    "32400":6,
                    "97200":1,
                    "291600":10,
                    "874800":10,
                    "2624400":4,
                    "7873200":206,
                    "23619600":36,
                    "70858800":194,
                    "212576400":0
                },
                "isDisabled":false
            },

The NPM algorithm is relatively simple: a score is the weighted average of components, themselves often nested averages.

maintenance, the section in question, has a 35% weight on the master score, and openIssues is 20% of maintenance. The fsl repo is scored 0.17 on openIssues, meaning those gh issues alone drag the total score down by 7% from an ideal 1.0.

@conartist6 - frankly I think it’s a stupid system