Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 18:08 UTC

codetalcott / mojo-http

Realtime from a plain sync Django or Flask view: hold an SSE stream or WebSocket with two response headers. A WSGI/ASGI server written in Mojo — pip install m0serve. On one machine: no Channels, no Redis, no daphne. Across machines: Postgres NOTIFY.

Mojo · PythonMIT★ 6 stars⑂ 1 forksince Aug 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

codetalcott/mojo-http holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (83/100) and lowest on Community & Adoption (35/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

Wm TalcottPersonal account
0 followers14 public repossince Oct 2017

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
PyPIm00.15.0474172 days agodatastarhtmxhttpmojoserversse
PyPIm0serve1.18.0785342 days agoasgidjangomojoserverssewebsocketwsgi

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
13.8/36Commit cadence — 20/52 weeks with commits
18/18Commit volume — 2,234 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,234
human_commit_share0.77
days_since_last_push2
active_weeks_last_year20
How it's scored
27/27Ships releases — 43 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~5.2 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count43
latest_release_tagv1.18.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases5.2

Community & Adoption

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

35Weak · 17% of overall
How it's scored
11.3/60Stars — 6 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars6
watchers0
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
41.3/80Monthly downloads — 1,259 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesm0, m0serve
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,259
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 factor — 1 contributor(s) cover half of all commits
1.5/22.5Commit distribution — top contributor authored 94% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.935
How it's scored
36/42Issue resolution — 86% of issues closed
29.4/30PR acceptance — 674/688 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 11/12 approved changesets -- score normalized to 9
Inputs used
merged_prs674
open_issues3
closed_issues18
prs_merged_7d21
prs_decided_7d21
prs_merged_30d51
prs_decided_30d52
issue_closed_ratio0.857
closed_unmerged_prs14
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
0/25Owner reach — 0 followers of codetalcott
20.6/25Track record — 14 public repos, account ~9 yr old
Inputs used
followers0
owner_typeUser
is_verified—
owner_logincodetalcott
public_repos14
account_age_days3,318
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on pypi
35/35Publish recency — latest publish 2 days ago
20/20Version history — 34 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesm0, m0serve
ecosystemspypi
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows — 10 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://m0serve.dev
10/10Repository description
10/10Topics — 18 topics
10/10Wiki
Inputs used
topicsdatastar, http-server, hypermedia, mojo, mojo-lang, server-sent-events, sse, web-framework, lightbug-http, asgi, asgi-server, django, flask, python, realtime, websockets, wsgi, wsgi-server
has_wikiyes
homepagehttps://m0serve.dev
docs_sitehttps://m0serve.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 12 out of 12 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
6.8/7.5Code-Review — Found 11/12 approved changesets -- score normalized to 9
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — 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 17 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
4.5/7.5Vulnerabilities — 4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.5

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories4
affected_packages1
assessed_packages67
unassessed_packages1
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 67 resolved dependencies against OSV. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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
45/45Agent instructions — CLAUDE.md, packages/m0-datastar/AGENTS.md, packages/m0-datastar/CLAUDE.md, packages/m0-postgres/AGENTS.md, packages/m0-postgres/CLAUDE.md, packages/m0-sqlite/AGENTS.md, packages/m0-sqlite/CLAUDE.md, packages/m0-wsgi/AGENTS.md, packages/m0-wsgi/CLAUDE.md, packaging/m0/AGENTS.md, packaging/m0/CLAUDE.md, packaging/m0/src/m0/templates/_common/AGENTS.md, packaging/m0/src/m0/templates/_common/CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 68 of 77 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.883
agent_instruction_filesCLAUDE.md, packages/m0-datastar/AGENTS.md, packages/m0-datastar/CLAUDE.md, packages/m0-postgres/AGENTS.md, packages/m0-postgres/CLAUDE.md, packages/m0-sqlite/AGENTS.md, packages/m0-sqlite/CLAUDE.md, packages/m0-wsgi/AGENTS.md, packages/m0-wsgi/CLAUDE.md, packaging/m0/AGENTS.md, packaging/m0/CLAUDE.md, packaging/m0/src/m0/templates/_common/AGENTS.md, packaging/m0/src/m0/templates/_common/CLAUDE.md
agent_instruction_max_bytes69,301
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 56 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 2 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.56
toolchain_manifests—
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable code — Mojo without a type-check config
53.7/55Manageable file sizes — 6/260 source files over 60KB
Inputs used
primary_languageMojo
largest_source_bytes174,904
source_files_sampled260
oversized_source_files6

Key facts

6GitHub stars
2contributors
2,234commits, last 12 months
2days since last push
43releases
1bus factor
3open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'mojo-http' from its registry
  • deps.dev does not index pypi:m0@0.15.0; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-11-21 18:08 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 11/12 approved changesets -- score normalized to 9
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6Vulnerabilities4 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPImojo==1.2.0pyproject.toml
All dependencies 68

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

RegistryPackageVersionRelation
PyPImojo1.2.0direct
PyPIannotated-doc0.0.5indirect
PyPIannotated-types0.8.0indirect
PyPIanyio4.14.2indirect
PyPIasgiref3.12.1indirect
PyPIbeautifulsoup44.15.0indirect
PyPIblinker1.9.0indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIdjango5.2.19indirect
PyPIexceptiongroup1.3.1indirect
PyPIfastapi0.162.5indirect
PyPIfastcore2.2.14indirect
PyPIflask3.1.3indirect
PyPIgranian2.8.8indirect
PyPIh110.16.0indirect
PyPIhatchling—indirect
PyPIhttpcore22.12.0indirect
PyPIhttptools0.8.0indirect
PyPIhttpx22.12.0indirect
PyPIhttpx2-jsfetch1.0indirect
PyPIidna3.19indirect
PyPIitsdangerous2.2.0indirect
PyPIjinja23.1.6indirect
PyPImarkdown-it-py4.3.0indirect
PyPImarkupsafe3.0.3indirect
PyPImax-core26.7.0indirect
PyPImax-mojo-libs26.7.0indirect
PyPImblack26.7.0indirect
PyPImdurl0.1.2indirect
PyPImojo-compiler1.2.0indirect
PyPImojo-compiler-mojo-libs1.2.0indirect
PyPImojo-http1.18.0indirect
PyPImojo-lldb-libs1.2.0indirect
PyPImypy-extensions1.1.0indirect
PyPInumpy2.2.6indirect
PyPInumpy2.4.6indirect
PyPInumpy2.5.3indirect
PyPIoauthlib4.0.1indirect
PyPIopentelemetry-api1.45.2indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.11.2indirect
PyPIpoethepoet0.49.0indirect
PyPIpsycopg3.2.13indirect
PyPIpsycopg-binary3.2.13indirect
PyPIpydantic2.13.5indirect
PyPIpydantic-core2.46.5indirect
PyPIpyflakes4.0.3indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-dotenv1.2.3indirect
PyPIpython-fasthtml0.14.23indirect
PyPIpython-multipart0.0.32indirect
PyPIpyyaml6.0.3indirect
PyPIsix1.17.0indirect
PyPIsoupsieve2.9.2indirect
PyPIsqlparse0.6.0indirect
PyPIstarlette1.6.0indirect
PyPItomli2.4.1indirect
PyPItruststore0.10.4indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPItzdata2026.3indirect
PyPIuvicorn0.52.4indirect
PyPIuvloop0.22.1indirect
PyPIwatchfiles1.2.0indirect
PyPIwebsockets16.1.1indirect
PyPIwebsockets17.0.1indirect
PyPIwerkzeug3.1.9indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 67 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
soupsieve2.9.2indirecthigh44.0.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 statistics — PyPI.