Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 18:00 UTC

DavidAnson / markdownlint-cli2

A fast, flexible, configuration-based command-line interface for linting Markdown/CommonMark files with the markdownlint library

JavaScriptMIT★ 910 stars⑂ 81 forkssince Jul 2020View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

DavidAnson/markdownlint-cli2 holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on AI Readiness (39/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

David AnsonPersonal account
741 followers37 public repossince Jun 2012@Microsoft @Azure

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?

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
33.2/36Commit cadence48/52 weeks with commits
18/18Commit volume330 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year330
human_commit_share0.52
days_since_last_push1
active_weeks_last_year48
How it's scored
16.2/27Ships releases55 version tags (no GitHub releases)
36/36Release recencylatest release 31 days ago
19.8/27Release cadencea release every ~48.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count55
latest_release_tagv0.23.2
releases_from_tagsyes
days_since_latest_release31
mean_days_between_releases48.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?

77Good · 17% of overall
How it's scored
48/60Stars910 stars
15.9/25Forks81 forks
4.7/15Watchers8 watchers
Inputs used
forks81
stars910
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads12,392,602 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmarkdownlint-cli2, markdownlint-cli2-formatter-json, markdownlint-cli2-formatter-junit, markdownlint-cli2-formatter-sarif, markdownlint-cli2-formatter-pretty, markdownlint-cli2-formatter-default, markdownlint-cli2-formatter-template, markdownlint-cli2-formatter-summarize
dependents
ecosystemsnpm
total_downloads
monthly_downloads12,392,602
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 factor1 contributor(s) cover half of all commits
0.7/22.5Commit distributiontop contributor authored 97% of commits
13.5/13.5Contributor breadth16 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled16
top_contributor_share0.969
How it's scored
41.7/42Issue resolution99% of issues closed
27.5/30PR acceptance682/743 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/10 approved changesets -- score normalized to 0
Inputs used
merged_prs682
open_issues1
closed_issues163
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.994
closed_unmerged_prs61
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
20.6/25Owner reach741 followers of DavidAnson
23.5/25Track record37 public repos, account ~14 yr old
Inputs used
followers741
owner_typeUser
is_verified
owner_loginDavidAnson
public_repos37
account_age_days5,193
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable8 package(s) on npm
35/35Publish recencylatest publish 31 days ago
20/20Version history56 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmarkdownlint-cli2, markdownlint-cli2-formatter-json, markdownlint-cli2-formatter-junit, markdownlint-cli2-formatter-sarif, markdownlint-cli2-formatter-pretty, markdownlint-cli2-formatter-default, markdownlint-cli2-formatter-template, markdownlint-cli2-formatter-summarize
ecosystemsnpm
any_deprecatedno
min_days_since_publish31

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter configeslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests16 out of 16 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
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsmarkdown, lint, nodejs, commonmark
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

71Good · 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-Tests16 out of 16 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/7.5Code-ReviewFound 0/10 approved changesets -- score normalized to 0
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
7.5/7.5Maintained30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.4
Excluded from scoring (no data or not applicable): Branch-Protection, 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
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages85
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:markdownlint-cli2@0.23.2 runtime dependency closure — what installing the published package pulls in — 85 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.

39Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.docker.com/llms.txt)
1/40Legible commit history1 of 52 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.docker.com/llms.txt
legible_history_share0.019
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.mjs
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance48 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.48
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/137 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes44,492
source_files_sampled137
oversized_source_files0

Key facts

910GitHub stars
16contributors
330commits, last 12 months
1days since last push
55releases
1bus factor
1open 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 ★ / 81 ⇿
0Stars
81Forks
47Releases

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.

0204060807932020-092023-082026-08
Major 0Minor 23Patch 24

Each point covers 6 days.

OpenSSF Scorecard 6.4 / 10
6.4aggregate

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-27 18:00 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-Tests16 out of 16 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 4 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 7 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
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 11
RegistryPackageVersion constraintManifest
npmjunit-report-builder5.1.2formatter-junit/package.json
npmterminal-link5.0.0formatter-pretty/package.json
npmglobby16.2.2package.json
npmjs-yaml5.2.2package.json
npmjsonc-parser3.3.1package.json
npmjsonpointer5.0.1package.json
npmmarkdown-it14.3.0package.json
npmmarkdownlint-cli2-formatter-default0.0.6package.json
npmmarkdownlint0.41.1package.json
npmmicromatch4.0.8package.json
npmsmol-toml1.7.0package.json
All dependencies 34

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

RegistryPackageVersionRelation
npmglobby16.2.1direct
npmjs-yaml5.2.2direct
npmjsonc-parser3.3.1direct
npmjsonpointer5.0.1direct
npmjunit-report-builder5.1.2direct
npmmarkdown-it14.3.0direct
npmmarkdownlint0.41.1direct
npmmarkdownlint-cli2-formatter-default0.0.6direct
npmmicromatch4.0.8direct
npmsmol-toml1.7.0direct
npmterminal-link5.0.0direct
npm@eslint/js10.0.1indirect
npm@playwright/test1.61.1indirect
npm@stylistic/eslint-plugin5.10.0indirect
npmajv8.20.0indirect
npmconcurrently10.0.3indirect
npmcpy13.2.2indirect
npmcpy-cli7.0.0indirect
npmeslint10.7.0indirect
npmeslint-node-test0.2.0indirect
npmeslint-plugin-jsdoc63.0.13indirect
npmeslint-plugin-n18.2.2indirect
npmeslint-plugin-unicorn71.1.0indirect
npmexeca9.6.1indirect
npmmarkdown-it-emoji3.0.0indirect
npmmarkdown-it-for-inline2.0.1indirect
npmmarkdownlint-cli2-formatter-codequality0.0.7indirect
npmmarkdownlint-cli2-formatter-json0.0.9indirect
npmmarkdownlint-cli2-formatter-junit0.0.14indirect
npmmarkdownlint-cli2-formatter-pretty0.0.10indirect
npmmarkdownlint-cli2-formatter-sarif0.0.4indirect
npmmarkdownlint-cli2-formatter-summarize0.0.8indirect
npmmarkdownlint-cli2-formatter-template0.0.4indirect
npmmarkdownlint-rule-extended-ascii0.2.1indirect
Dependency advisories 0

Installing npm:markdownlint-cli2@0.23.2 pulls in 85 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 statisticsnpm.