Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 17:16 UTC

frostming / marko

A markdown parser with high extensibility.

PythonMIT★ 465 stars⑂ 53 forkssince Aug 2018View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

frostming/marko holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (92/100) and lowest on Security (50/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Frost MingPersonal account
1,702 followers127 public repossince Dec 2015

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 publish
PyPImarko2.2.46,401,3674715 days ago

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
28.8/36Push recencylast push 9 days ago
6.2/36Commit cadence9/52 weeks with commits
13.1/18Commit volume28 commits in the last year
6/10OpenSSF Scorecard: Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year28
human_commit_share0.55
days_since_last_push9
active_weeks_last_year9
How it's scored
27/27Ships releases16 releases published
27/36Release recencylatest release 91 days ago
19.8/27Release cadencea release every ~91.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count16
latest_release_tagv2.2.3
releases_from_tagsno
days_since_latest_release91
mean_days_between_releases91.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?

67Good · 17% of overall
How it's scored
43.3/60Stars465 stars
14.3/25Forks53 forks
3.9/15Watchers6 watchers
Inputs used
forks53
stars465
watchers6
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_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads6,401,367 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmarko
dependents
ecosystemspypi
total_downloads
monthly_downloads6,401,367
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?

69Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.8/22.5Commit distributiontop contributor authored 83% of commits
13.5/13.5Contributor breadth27 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled27
top_contributor_share0.832
How it's scored
41.1/42Issue resolution98% of issues closed
24.3/30PR acceptance149/184 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 10/19 approved changesets -- score normalized to 5
Inputs used
merged_prs149
open_issues2
closed_issues90
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.978
closed_unmerged_prs35
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
23.2/25Owner reach1,702 followers of frostming
25/25Track record127 public repos, account ~10 yr old
Inputs used
followers1,702
owner_typeUser
is_verified
owner_loginfrostming
public_repos127
account_age_days3,906
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 pypi
35/35Publish recencylatest publish 15 days ago
20/20Version history47 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmarko
ecosystemspypi
any_deprecatedno
min_days_since_publish15

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.isort]), setup.cfg ([flake8])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests16 out of 26 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://marko-py.readthedocs.io/
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsmarkdown, commonmark, parser, regexp, extensible
has_wikiyes
homepagehttps://marko-py.readthedocs.io/
docs_sitehttps://marko-py.readthedocs.io/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.5/2.5CI-Tests16 out of 26 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 10/19 approved changesets -- score normalized to 5
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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
4.5/7.5Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
0/7.5Vulnerabilities21 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.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
advisories40
affected_packages5
assessed_packages29
unassessed_packages0
affected_by_severityhigh 4, moderate 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 29 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.

69Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history50 of 55 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.909
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapdocs/Makefile, noxfile.py
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.isort]), setup.cfg ([flake8])
11/11Static type checkingmarko/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespdm.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile, noxfile.py
has_devcontainerno
has_linter_configyes
typecheck_configsmarko/py.typed
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (marko/py.typed)
55/55Manageable file sizes0/36 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes23,385
source_files_sampled36
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples, samples
Inputs used
example_dirsexamples, samples
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

465GitHub stars
27contributors
28commits, last 12 months
9days since last push
16releases
1bus factor
2open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 53 ⇿
0Stars
53Forks
16Releases

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.

01020304050605322019-042022-112026-07
Major 1Minor 3Patch 12

Each point covers 7 days.

OpenSSF Scorecard 3.8 / 10
3.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-27 17:15 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
6CI-Tests16 out of 26 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 10/19 approved changesets -- score normalized to 5
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
0Vulnerabilities21 existing vulnerabilities detected
All dependencies 29

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

RegistryPackageVersionRelation
PyPIalabaster0.7.16indirect
PyPIbabel2.17.0indirect
PyPIcertifi2023.5.7indirect
PyPIcharset-normalizer3.1.0indirect
PyPIcolorama0.4.6indirect
PyPIdocutils0.21.2indirect
PyPIidna3.4indirect
PyPIimagesize1.4.1indirect
PyPIimportlib-metadata8.7.0indirect
PyPIjinja23.1.2indirect
PyPImarkupsafe2.1.3indirect
PyPIpackaging25.0indirect
PyPIpygments2.20.0indirect
PyPIpygments-styles0.2.0indirect
PyPIpython-slugify8.0.4indirect
PyPIrequests2.31.0indirect
PyPIshibuya2025.10.21indirect
PyPIsnowballstemmer2.2.0indirect
PyPIsphinx7.4.7indirect
PyPIsphinxcontrib-applehelp1.0.2indirect
PyPIsphinxcontrib-devhelp1.0.2indirect
PyPIsphinxcontrib-htmlhelp2.0.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp1.0.3indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItext-unidecode1.3indirect
PyPItomli2.3.0indirect
PyPIurllib32.0.3indirect
PyPIzipp3.23.0indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
certifi2023.5.7indirecthigh42024.7.4
idna3.4indirecthigh43.15
jinja23.1.2indirecthigh103.1.6
urllib32.0.3indirecthigh162.7.0
requests2.31.0indirectmoderate62.33.0

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