Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 19:13 UTC

itercharles / MedHarness

Design-control checks for software teams — traceability, verification, SOUP and releases, as CI gates.

PythonMIT★ 3 stars⑂ 1 forksince Nov 2025View on GitHub ↗
KindCommand-line toolPluginLibraryhow this is determined

itercharles/MedHarness holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (82/100) and lowest on Community & Adoption (49/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

CharlesPersonal account
3 followers6 public repossince Aug 2013Elekta

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
PyPImedharness0.82.03,5161591 day agomedical-deviceiec-62304iso-14971iec-82304-1dhfdesign-history-filetraceabilitycompliancesamd

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
13.2/36Commit cadence — 19/52 weeks with commits
18/18Commit volume — 376 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year376
human_commit_share0.99
days_since_last_push1
active_weeks_last_year19
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~1.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv0.82.0
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases1.1

Community & Adoption

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

49Weak · 17% of overall
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
47.3/80Monthly downloads — 3,516 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmedharness
dependents—
ecosystemspypi
total_downloads—
monthly_downloads3,516
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% 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.989
How it's scored
0/42Issue resolution — no issues or no data
29.4/30PR acceptance — 483/493 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs483
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d36
prs_decided_30d36
issue_closed_ratio—
closed_unmerged_prs10
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
4.3/25Owner reach — 3 followers of itercharles
18.2/25Track record — 6 public repos, account ~13 yr old
Inputs used
followers3
owner_typeUser
is_verified—
owner_loginitercharles
public_repos6
account_age_days4,839
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 pypi
35/35Publish recency — latest publish 1 days ago
20/20Version history — 159 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmedharness
ecosystemspypi
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
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_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://github.com/itercharles/MedHarness
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicscompliance, design-history-file, dhf, medical-device, python, samd, traceability
has_wikino
homepagehttps://github.com/itercharles/MedHarness
docs_sitehttps://github.com/itercharles/MedHarness
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
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/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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.
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6.7

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_packages2
assessed_packages44
unassessed_packages0
affected_by_severitycritical 2
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 44 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.

63Moderate · 4% of overall
How it's scored
45/45Agent instructions — .cursor/rules/agent.mdc, .github/copilot-instructions.md, AGENTS.md, CLAUDE.md, docs/agents.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 96 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.97
agent_instruction_files.cursor/rules/agent.mdc, .github/copilot-instructions.md, AGENTS.md, CLAUDE.md, docs/agents.md
agent_instruction_max_bytes9,563
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 99 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.99
toolchain_manifests—
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable code — Python without a type-check config
54.8/55Manageable file sizes — 1/255 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes63,619
source_files_sampled255
oversized_source_files1

Key facts

3GitHub stars
2contributors
376commits, last 12 months
1days since last push
100releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:medharness@0.82.0; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 6.7 / 10
6.7aggregate

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 19:13 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
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/30 approved changesets -- score normalized to 0
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
10Maintained30 commit(s) and 0 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
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPIpydantic>=2.0pyproject.toml
PyPIclick—pyproject.toml
PyPInetworkx—pyproject.toml
PyPIpyyaml—pyproject.toml
PyPIjinja2—pyproject.toml
PyPImarkdown—pyproject.toml
All dependencies 44

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

RegistryPackageVersionRelation
PyPIclick8.3.3direct
PyPIjinja23.1.6direct
PyPImarkdown3.10.2direct
PyPInetworkx3.6.1direct
PyPIpydantic2.13.4direct
PyPIpyyaml6.0.3direct
PyPIannotated-types0.7.0indirect
PyPIattrs26.1.0indirect
PyPIbrotli1.2.0indirect
PyPIbrotlicffi1.2.0.1indirect
PyPIbuild1.5.0indirect
PyPIcffi2.0.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.14.0indirect
PyPIcssselect20.9.0indirect
PyPIexecnet2.1.2indirect
PyPIfonttools4.62.1indirect
PyPIiniconfig2.3.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPImarkupsafe3.0.3indirect
PyPImedharness0.82.0indirect
PyPIpackaging26.2indirect
PyPIpillow13.0.0indirect
PyPIpluggy1.6.0indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.46.4indirect
PyPIpydyf0.12.1indirect
PyPIpygments2.20.0indirect
PyPIpyphen0.17.2indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIreferencing0.37.0indirect
PyPIrpds-py2026.6.3indirect
PyPItinycss21.5.1indirect
PyPItinyhtml52.1.0indirect
PyPItomli2.4.1indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPIweasyprint70.0indirect
PyPIwebencodings0.5.1indirect
PyPIzopfli0.4.1indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
brotli1.2.0indirectcritical21.2.1.0
brotlicffi1.2.0.1indirectcritical21.2.1.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.