Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 10:04 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. No Channels, no Redis, no daphne.

Mojo · PythonMIT★ 2 stars⑂ 1 forksince Aug 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

codetalcott/mojo-http holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Engineering Quality (81/100) and lowest on Community & Adoption (32/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Wm TalcottPersonal account
8 followers21 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
PyPIm0serve1.4.03,055192 days agoasgidjangomojoserverssewebsocketwsgi

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
8.3/36Commit cadence12/52 weeks with commits
18/18Commit volume949 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year949
human_commit_share0.7
days_since_last_push0
active_weeks_last_year12
How it's scored
27/27Ships releases28 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~1.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count28
latest_release_tagv1.4.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases1.7

Community & Adoption

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

32At Risk · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars2
watchers0
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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
46.5/80Monthly downloads3,055 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesm0serve
dependents
ecosystemspypi
total_downloads
monthly_downloads3,055
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2/22.5Commit distributiontop contributor authored 91% of commits
2.7/13.5Contributor breadth2 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.911
How it's scored
42/42Issue resolution100% of issues closed
29.4/30PR acceptance323/330 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 9/11 approved changesets -- score normalized to 8
Inputs used
merged_prs323
open_issues0
closed_issues9
prs_merged_7d53
prs_decided_7d55
prs_merged_30d56
prs_decided_30d58
issue_closed_ratio1
closed_unmerged_prs7
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
6.9/25Owner reach8 followers of codetalcott
21.8/25Track record21 public repos, account ~8 yr old
Inputs used
followers8
owner_typeUser
is_verified
owner_logincodetalcott
public_repos21
account_age_days3,254
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 2 days ago
20/20Version history19 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesm0serve
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 workflows9 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests11 out of 11 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 sitehttps://m0serve.dev
10/10Repository description
10/10Topics18 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?

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests11 out of 11 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
6/7.5Code-ReviewFound 9/11 approved changesets -- score normalized to 8
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
5/5Packagingpackaging workflow detected
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5

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
advisories0
affected_packages0
assessed_packages64
unassessed_packages1
affected_by_severitynone
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 64 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.

67Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt present
40/40Legible commit history63 of 70 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url
legible_history_share0.9
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes124,356
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice58 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.58
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeMojo without a type-check config
53.9/55Manageable file sizes3/145 source files over 60KB
Inputs used
primary_languageMojo
largest_source_bytes91,282
source_files_sampled145
oversized_source_files3

Key facts

2GitHub stars
2contributors
949commits, last 12 months
0days since last push
28releases
1bus factor
0open 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

More detail

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-09-18 10:04 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 9/11 approved changesets -- score normalized to 8
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPImojo==1.0.0pyproject.toml
All dependencies 65

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

RegistryPackageVersionRelation
PyPImojo1.0.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.17indirect
PyPIdjango6.1indirect
PyPIexceptiongroup1.3.1indirect
PyPIfastapi0.141.1indirect
PyPIfastcore2.2.14indirect
PyPIflask3.1.3indirect
PyPIgranian2.8.2indirect
PyPIh110.16.0indirect
PyPIhatchlingindirect
PyPIhttpcore22.12.0indirect
PyPIhttptools0.8.0indirect
PyPIhttpx22.12.0indirect
PyPIhttpx2-jsfetch1.0indirect
PyPIidna3.19indirect
PyPIitsdangerous2.2.0indirect
PyPIjinja23.1.6indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImblack26.5.0indirect
PyPImdurl0.1.2indirect
PyPImojo-compiler1.0.0indirect
PyPImojo-compiler-mojo-libs1.0.0indirect
PyPImojo-http1.4.0indirect
PyPImojo-lldb-libs1.0.0indirect
PyPImypy-extensions1.1.0indirect
PyPInumpy2.2.6indirect
PyPInumpy2.4.6indirect
PyPInumpy2.5.3indirect
PyPIoauthlib3.3.1indirect
PyPIpastel0.2.1indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.11.2indirect
PyPIpoethepoet0.48.0indirect
PyPIpydantic2.13.5indirect
PyPIpydantic-core2.46.5indirect
PyPIpyflakes3.4.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-dotenv1.2.3indirect
PyPIpython-fasthtml0.14.13indirect
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.8indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 64 packages, which also include development and test pins that never ship: 0 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.

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