Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-03 10:55 UTC

JustinBeckwith / linkinator

Broken link checker that crawls websites and validates links. Find broken links, dead links, and invalid URLs in websites, documentation, and local files. Perfect for SEO audits and CI/CD.

TypeScriptMIT★ 1,269 stars⑂ 110 forkssince Feb 2019View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

JustinBeckwith/linkinator holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (89/100) and lowest on Sustainability & Governance (67/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

89
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.

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

Ownership

Justin BeckwithPersonal account
749 followers245 public repossince Dec 2010@OpenAI

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

Package ecosystems

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
24.2/36Commit cadence — 35/52 weeks with commits
18/18Commit volume — 179 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year179
human_commit_share0.23
days_since_last_push4
active_weeks_last_year35
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 35 days ago
27/27Release cadence — a release every ~27.3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_taglinkinator-v8.1.0
releases_from_tagsno
days_since_latest_release35
mean_days_between_releases27.3

Community & Adoption

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

71Good · 17% of overall
How it's scored
50.3/60Stars — 1,269 stars
17/25Forks — 110 forks
4.3/15Watchers — 7 watchers
Inputs used
forks110
stars1,269
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
77.9/80Monthly downloads — 691,210 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslinkinator
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads691,210
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?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.4/22.5Commit distribution — top contributor authored 80% of commits
13.5/13.5Contributor breadth — 26 contributors
10/10OpenSSF Scorecard: Contributors — project has 14 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled26
top_contributor_share0.803
How it's scored
40.8/42Issue resolution — 97% of issues closed
24/30PR acceptance — 507/633 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/10 approved changesets -- score normalized to 0
Inputs used
merged_prs507
open_issues5
closed_issues165
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.971
closed_unmerged_prs126
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
20.7/25Owner reach — 749 followers of JustinBeckwith
25/25Track record — 245 public repos, account ~15 yr old
Inputs used
followers749
owner_typeUser
is_verified—
owner_loginJustinBeckwith
public_repos245
account_age_days5,762
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 35 days ago
20/20Version history — 142 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslinkinator
ecosystemsnpm
any_deprecatedno
min_days_since_publish35

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 16 topics
0/10Wiki
Inputs used
topicslink-checker, typescript, broken-links, 404, broken-link-checker, seo-tools, seo, dead-links, link-validator, url-validator, website-crawler, web-crawler, html, ci-cd, testing, nodejs
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?

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/10 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 14 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages24
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:linkinator@8.1.0 runtime dependency closure — what installing the published package pulls in — 24 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 23 of 23 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes12,360
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 70 of the last 100 commits are automated dependency updates
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.7
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/43 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes55,606
source_files_sampled43
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — samples
Inputs used
example_dirssamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,269GitHub stars
26contributors
179commits, last 12 months
4days since last push
100releases
1bus factor
5open 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 ★ / 110 ⇿
0Stars
110Forks
100Releases

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.

02040608010012010852019-042022-122026-09
Major 5Minor 21Patch 56

Each point covers 7 days.

OpenSSF Scorecard 6.9 / 10
6.9aggregate

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-10-03 10:55 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-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/10 approved changesets -- score normalized to 0
10Contributorsproject has 14 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities13 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
npmchalk^6.0.0package.json
npmescape-html^1.0.3package.json
npmglob^13.0.0package.json
npmhtmlparser2^12.0.0package.json
npmmarked^18.0.0package.json
npmmarked-gfm-heading-id^4.1.4package.json
npmmeow^14.0.0package.json
npmmime^4.0.0package.json
npmsaxes6.0.0package.json
npmsrcset^5.0.0package.json
npmundici^8.0.0package.json
All dependencies 152

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

RegistryPackageVersionRelation
npmchalk6.0.0direct
npmescape-html1.0.3direct
npmglob13.0.6direct
npmhtmlparser212.0.0direct
npmmarked18.0.5direct
npmmarked-gfm-heading-id4.1.4direct
npmmeow14.1.0direct
npmmime4.1.0direct
npmsaxes6.0.0direct
npmsrcset5.0.3direct
npmundici8.9.0direct
npm@babel/helper-string-parser7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@babel/parser7.29.8indirect
npm@babel/types7.29.8indirect
npm@bcoe/v8-coverage1.0.2indirect
npm@biomejs/biome2.4.4indirect
npm@biomejs/cli-darwin-arm642.4.4indirect
npm@biomejs/cli-darwin-x642.4.4indirect
npm@biomejs/cli-linux-arm642.4.4indirect
npm@biomejs/cli-linux-arm64-musl2.4.4indirect
npm@biomejs/cli-linux-x642.4.4indirect
npm@biomejs/cli-linux-x64-musl2.4.4indirect
npm@biomejs/cli-win32-arm642.4.4indirect
npm@biomejs/cli-win32-x642.4.4indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.6.0indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@oxc-project/types0.149.0indirect
npm@rolldown/binding-android-arm-eabi1.2.8indirect
npm@rolldown/binding-android-arm641.2.8indirect
npm@rolldown/binding-darwin-arm641.2.8indirect
npm@rolldown/binding-darwin-x641.2.8indirect
npm@rolldown/binding-freebsd-x641.2.8indirect
npm@rolldown/binding-linux-arm-gnueabihf1.2.8indirect
npm@rolldown/binding-linux-arm64-gnu1.2.8indirect
npm@rolldown/binding-linux-arm64-musl1.2.8indirect
npm@rolldown/binding-linux-ppc64-gnu1.2.8indirect
npm@rolldown/binding-linux-s390x-gnu1.2.8indirect
npm@rolldown/binding-linux-x64-gnu1.2.8indirect
npm@rolldown/binding-linux-x64-musl1.2.8indirect
npm@rolldown/binding-openharmony-arm641.2.8indirect
npm@rolldown/binding-win32-arm64-msvc1.2.8indirect
npm@rolldown/binding-win32-x64-msvc1.2.8indirect
npm@rolldown/pluginutils1.0.1indirect
npm@sec-ant/readable-stream0.4.1indirect
npm@sindresorhus/merge-streams4.0.0indirect
npm@types/chai5.2.3indirect
npm@types/deep-eql4.0.2indirect
npm@types/escape-html1.0.4indirect
npm@types/estree1.0.9indirect
npm@types/node25.3.0indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npm@vitest/coverage-v85.0.0indirect
npm@vitest/istanbul-lib-coverage1.0.1indirect
npm@vitest/istanbul-lib-report1.0.1indirect
npm@vitest/mocker5.0.0indirect
npm@vitest/spy5.0.0indirect
npmansi-regex6.2.2indirect
npmassertion-error2.0.1indirect
npmast-v8-to-istanbul1.0.6indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion5.0.9indirect
npmchai6.2.2indirect
npmdetect-libc2.1.2indirect
npmdom-serializer3.0.0indirect
npmdomelementtype3.0.0indirect
npmdomhandler6.0.1indirect
npmdomutils4.0.2indirect
npmentities8.0.0indirect
npmes-module-lexer2.3.2indirect
npmestree-walker3.0.3indirect
npmexeca10.0.0indirect
npmexpect-type1.4.0indirect
npmfdir6.5.0indirect
npmfigures6.1.0indirect
npmfsevents2.3.3indirect
npmget-stream9.0.1indirect
npmgithub-slugger2.0.0indirect
npmhuman-signals8.0.1indirect
npmhusky9.1.7indirect
npmis-plain-obj4.1.0indirect
npmis-stream4.0.1indirect
npmis-unicode-supported2.1.0indirect
npmjs-tokens10.0.0indirect
npmlightningcss1.33.0indirect
npmlightningcss-android-arm641.33.0indirect
npmlightningcss-darwin-arm641.33.0indirect
npmlightningcss-darwin-x641.33.0indirect
npmlightningcss-freebsd-x641.33.0indirect
npmlightningcss-linux-arm-gnueabihf1.33.0indirect
npmlightningcss-linux-arm64-gnu1.33.0indirect
npmlightningcss-linux-arm64-musl1.33.0indirect
npmlightningcss-linux-x64-gnu1.33.0indirect
npmlightningcss-linux-x64-musl1.33.0indirect
npmlightningcss-win32-arm64-msvc1.33.0indirect
npmlightningcss-win32-x64-msvc1.33.0indirect
npmlru-cache11.2.6indirect
npmmagic-string1.3.1indirect
npmmagicast0.5.5indirect
npmminimatch10.2.4indirect
npmminipass7.1.3indirect
npmnanoid3.3.19indirect
npmnpm-run-path6.0.0indirect
npmobug2.2.1indirect
npmparse-ms4.0.0indirect
npmpath-key4.0.0indirect
npmpath-scurry2.0.2indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.7indirect
npmpostcss8.5.28indirect
npmpretty-ms9.3.0indirect
npmrolldown1.2.8indirect
npmsiginfo2.0.0indirect
npmsignal-exit4.1.0indirect
npmsource-map-js1.2.1indirect
npmstackback0.0.2indirect
npmstd-env4.2.0indirect
npmstrip-ansi7.1.2indirect
npmstrip-final-newline4.0.0indirect
npmtinybench6.1.4indirect
npmtinyexec1.3.0indirect
npmtinyglobby0.2.17indirect
npmtinyrainbow3.1.1indirect
npmtypescript7.0.2indirect
npmundici-types7.18.2indirect
npmunicorn-magic0.3.0indirect
npmvite8.3.0indirect
npmvitest5.0.0indirect
npmwhich-command0.1.0indirect
npmwhy-is-node-running2.3.0indirect
npmxmlchars2.2.0indirect
npmyoctocolors2.1.2indirect
Dependency advisories 0

Installing npm:linkinator@8.1.0 pulls in 24 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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 statistics — npm.