Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-23 12:51 UTC

fiverr / statistician

📊 Create and compare files stats, and webpack bundle stats

JavaScriptMIT★ 8 stars⑂ 1 forksince Oct 2018View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

fiverr/statistician holds a health index of 39 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (57/100) and lowest on AI Readiness (24/100). It was last updated 65 days ago. A single contributor accounts for most of its recent work.

39
overall / 100
Weak

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

39
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 43 is calibrated to 39 on the published index scale (record calibration 2026-08-02).

Ownership

FiverrOrganization
122 followers101 public repossince May 2011

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmstatistician1.2.03,57646373 days agowebpack-statsfile-sizepull-requestspackagebundleanalyzecompare-filessizes

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

29At Risk · 21% of overall
How it's scored
18/36Push recencylast push 65 days ago
2.1/36Commit cadence3/52 weeks with commits
6.3/18Commit volume4 commits in the last year
1/10OpenSSF Scorecard: Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year4
human_commit_share1
days_since_last_push65
active_weeks_last_year3
How it's scored
16.2/27Ships releases21 version tags (no GitHub releases)
0/36Release recencylatest release 940 days ago
12.6/27Release cadencea release every ~209.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count21
latest_release_tag1.1.0
releases_from_tagsyes
days_since_latest_release940
mean_days_between_releases209.1
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

41Weak · 17% of overall
How it's scored
13.7/60Stars8 stars
0/25Forks1 forks
9.3/15Watchers49 watchers
Inputs used
forks1
stars8
watchers49
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
47.4/80Monthly downloads3,576 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesstatistician
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,576
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

57Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.8/22.5Commit distributiontop contributor authored 70% of commits
12.2/13.5Contributor breadth9 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.698
How it's scored
21/42Issue resolution50% of issues closed
26/30PR acceptance13/15 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs13
open_issues2
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.5
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
15/25Owner reach122 followers of fiverr
25/25Track record101 public repos, account ~15 yr old
Inputs used
followers122
owner_typeOrganization
is_verifiedno
owner_loginfiverr
public_repos101
account_age_days5,600
How it's scored
25/25Published & resolvable1 package(s) on npm
14/35Publish recencylatest publish 373 days ago
20/20Version history46 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesstatistician
ecosystemsnpm
any_deprecatedno
min_days_since_publish373

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests3 out of 11 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicswebpack-stats, file-size, pull-requests, package, bundle, analyze, compare-files, sizes
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.5/2.5CI-Tests3 out of 11 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 8/30 approved changesets -- score normalized to 2
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
10.4/35Direct dependencies free of known advisories2 affected: jsonwebtoken 8.5.1 (high 8.1), marked 0.6.3 (high 7.5)
14.4/25Indirect dependencies free of known advisories1 affected: yargs-parser 16.1.0 (moderate 5.3)
26.3/40No advisories left outstanding3 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,210 days ago
Inputs used
sourceosv
advisories7
affected_packages3
assessed_packages40
unassessed_packages0
affected_by_severityhigh 2, moderate 1
direct_affected_packages2
Matched the npm:statistician@1.2.0 runtime dependency closure — what installing the published package pulls in — 40 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

24At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18.2/40Legible commit history15 of 44 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.341
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config.eslintrc
0/11Static type checking
0/10Reproducible environment
4.5/10Demonstrated agent practice1 of the last 44 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.023
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/47 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes2,200
source_files_sampled47
oversized_source_files0

Key facts

8GitHub stars
9contributors
4commits, last 12 months
65days since last push
21releases
1bus factor
2open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 3.6 / 10
3.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-23 12:51 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
2CI-Tests3 out of 11 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
npmawait-reduce^1.2.3package.json
npmbyte-size^5.0.1package.json
npmchai^4.2.0package.json
npmchunkalyse^0.5.1package.json
npmfingerprinting^1.0.1package.json
npmindex-require^1.0.0package.json
npmjsonwebtoken^8.5.1package.json
npmmarked^0.6.1package.json
npmnode-fetch^2.3.0package.json
npmyargs-parser^21.0.1package.json
All dependencies 15

Full resolved dependency set from the GitHub dependency graph: 10 direct and 5 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmawait-reduce^1.2.3direct
npmbyte-size^5.0.1direct
npmchai^4.2.0direct
npmchunkalyse^0.5.1direct
npmfingerprinting^1.0.1direct
npmindex-require^1.0.0direct
npmjsonwebtoken^8.5.1direct
npmmarked^0.6.1direct
npmnode-fetch^2.3.0direct
npmyargs-parser^21.0.1direct
npmasync-execute^1.0.1indirect
npmchai-string^1.5.0indirect
npmclear-module^3.1.0indirect
npmeslint^5.14.1indirect
npmmocha^6.0.0indirect
Dependency advisories 3

Installing npm:statistician@1.2.0 pulls in 40 packages, direct and transitive: 3 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
jsonwebtoken8.5.1directhigh39.0.0
marked0.6.3directhigh34.0.10
yargs-parser16.1.0indirectmoderate118.1.1

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.