Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 03:01 UTC

EvanHahn / HumanizeDuration.js

361000 becomes "6 minutes, 1 second"

JavaScriptUnlicense★ 1,731 stars⑂ 177 forkssince Jul 2013View on GitHub ↗

EvanHahn/HumanizeDuration.js holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (86/100) and lowest on AI Readiness (46/100). It was last updated 44 days ago. A single contributor accounts for most of its recent work.

80
overall / 100
Excellent

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.

80
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 68 is calibrated to 80 on the published index scale (record calibration 2026-08-02).

Ownership

Evan HahnPersonal account
706 followers418 public repossince May 2011@TryGhost

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmhumanize-duration3.34.012,524,9888244 days agohumanizedurationtimehoursminutessecondsdaysyearsmonths

Metrics by category

Vitality

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

55Moderate · 21% of overall
How it's scored
18/36Push recencylast push 44 days ago
4.8/36Commit cadence7/52 weeks with commits
13.1/18Commit volume28 commits in the last year
7/10OpenSSF Scorecard: Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year28
human_commit_share1
days_since_last_push44
active_weeks_last_year7
How it's scored
16.2/27Ships releases70 version tags (no GitHub releases)
36/36Release recencylatest release 44 days ago
12.6/27Release cadencea release every ~120.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count70
latest_release_tagv3.34.0
releases_from_tagsyes
days_since_latest_release44
mean_days_between_releases120.7
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?

86Excellent · 17% of overall
How it's scored
52.5/60Stars1,731 stars
18.7/25Forks177 forks
5.6/15Watchers11 watchers
Inputs used
forks177
stars1,731
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Unlicense)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads12,524,988 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageshumanize-duration
dependents
ecosystemsnpm
total_downloads
monthly_downloads12,524,988
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth65 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled65
top_contributor_share0.865
How it's scored
42/42Issue resolution100% of issues closed
20.7/30PR acceptance89/129 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/30 approved changesets -- score normalized to 1
Inputs used
merged_prs89
open_issues0
closed_issues109
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs40
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
20.5/25Owner reach706 followers of EvanHahn
25/25Track record418 public repos, account ~15 yr old
Inputs used
followers706
owner_typeUser
is_verified
owner_loginEvanHahn
public_repos418
account_age_days5,574
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 44 days ago
20/20Version history82 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageshumanize-duration
ecosystemsnpm
any_deprecatedno
min_days_since_publish44

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.json, eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://evanhahn.github.io/HumanizeDuration.js/
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicshumanizeduration, duration, time
has_wikiyes
homepagehttps://evanhahn.github.io/HumanizeDuration.js/
docs_sitehttps://evanhahn.github.io/HumanizeDuration.js/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 4/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
5.2/7.5Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
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
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories5
affected_packages1
assessed_packages76
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 76 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
5.3/40Legible commit history10 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.json, eslint.config.mjs
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codeJavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes0/8 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes43,986
source_files_sampled8
oversized_source_files0

Key facts

1,731GitHub stars
65contributors
28commits, last 12 months
44days since last push
70releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 177 ⇿
0Stars
177Forks
69Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0408012016020017442013-072019-122026-06
Major 3Minor 42Patch 24

Each point covers 12 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-08-13 03:01 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
10CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/30 approved changesets -- score normalized to 1
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
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
8Vulnerabilities2 existing vulnerabilities detected
All dependencies 76

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

RegistryPackageVersionRelation
npm@eslint-community/eslint-utils4.9.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.23.3indirect
npm@eslint/config-helpers0.5.3indirect
npm@eslint/core1.1.1indirect
npm@eslint/js10.0.1indirect
npm@eslint/object-schema3.0.3indirect
npm@eslint/plugin-kit0.6.1indirect
npm@humanfs/core0.19.1indirect
npm@humanfs/node0.16.7indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@types/esrecurse4.3.1indirect
npm@types/estree1.0.8indirect
npm@types/json-schema7.0.15indirect
npm@types/ms2.1.0indirect
npm@types/node25.5.0indirect
npmacorn8.16.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.14.0indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.4indirect
npmcross-spawn7.0.6indirect
npmcsv-parse6.2.0indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmescape-string-regexp4.0.0indirect
npmeslint10.0.3indirect
npmeslint-scope9.1.2indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys5.0.1indirect
npmespree11.2.0indirect
npmesquery1.7.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfile-entry-cache8.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatted3.4.2indirect
npmglob-parent6.0.2indirect
npmglobals17.4.0indirect
npmignore5.3.2indirect
npmimurmurhash0.1.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmisexe2.0.0indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmminimatch10.2.4indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmprelude-ls1.2.1indirect
npmprettier3.8.1indirect
npmpunycode2.3.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmtype-check0.4.0indirect
npmtypescript5.9.3indirect
npmundici-types7.18.2indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 76 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion5.0.4indirecthigh55.0.9

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.31.0 — full methodology · metrics wiki.

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