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

pythonnet / clr-loader

Loader for different .NET runtimes

PythonMIT★ 43 stars⑂ 32 forkssince Oct 2019View on GitHub ↗

pythonnet/clr-loader holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Engineering Quality (76/100) and lowest on Community & Adoption (59/100). It was last updated 2 days 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

pythonnetOrganization
84 followers8 public repossince Nov 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIclr_loader0.3.13,058,95621131 days ago

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 2 days ago
9.7/36Commit cadence14/52 weeks with commits
15.3/18Commit volume50 commits in the last year
4/10OpenSSF Scorecard: Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year50
human_commit_share0.88
days_since_last_push2
active_weeks_last_year14
How it's scored
27/27Ships releases17 releases published
36/36Release recencylatest release 2 days ago
12.6/27Release cadencea release every ~159.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count17
latest_release_tagv0.3.1
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases159.8
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?

59Moderate · 17% of overall
How it's scored
26.3/60Stars43 stars
12.4/25Forks32 forks
2.7/15Watchers4 watchers
Inputs used
forks32
stars43
watchers4
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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads3,058,956 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesclr_loader
dependents
ecosystemspypi
total_downloads
monthly_downloads3,058,956
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.1/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth15 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.862
How it's scored
33.6/42Issue resolution80% of issues closed
23/30PR acceptance62/81 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/19 approved changesets -- score normalized to 1
Inputs used
merged_prs62
open_issues8
closed_issues32
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.8
closed_unmerged_prs19
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
30/30Ownership backingorganization-owned
0/20Verified domain
13.9/25Owner reach84 followers of pythonnet
18.9/25Track record8 public repos, account ~12 yr old
Inputs used
followers84
owner_typeOrganization
is_verifiedno
owner_loginpythonnet
public_repos8
account_age_days4,656

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 131 days ago
20/20Version history21 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesclr_loader
ecosystemspypi
any_deprecatedno
min_days_since_publish131

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests11 out of 12 merged PRs checked by a CI test -- score normalized to 9
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 sitehttps://pythonnet.github.io/clr-loader/
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsclr, dotnet, python, ffi
has_wikino
homepage
docs_sitehttps://pythonnet.github.io/clr-loader/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

61Moderate · 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.2/2.5CI-Tests11 out of 12 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/19 approved changesets -- score normalized to 1
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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
3/7.5Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): 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_packages2
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 pypi:clr_loader@0.3.1 runtime dependency closure — what installing the published package pulls in — 2 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.

63Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
24.2/40Legible commit history40 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.455
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapJustfile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingclr_loader/py.typed
10/10Reproducible environmentlockfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance12 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
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesJustfile
has_devcontainerno
has_linter_configno
typecheck_configsclr_loader/py.typed
agent_commit_share0.01
toolchain_manifestsexample/example.csproj, netfx_loader/ClrLoader.csproj
dependency_bot_commit_share0.12
How it's scored
27/45Type-checkable codePython with type-check config (clr_loader/py.typed)
52.5/55Manageable file sizes1/22 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes80,337
source_files_sampled22
oversized_source_files1
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 examplesexample
Inputs used
example_dirsexample
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

43GitHub stars
15contributors
50commits, last 12 months
2days since last push
17releases
1bus factor
8open issues
NuGet, 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 ★ / 32 ⇿
0Stars
32Forks
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.

01325383122020-012023-032026-05
Major 0Minor 1Patch 15

Each point covers 6 days.

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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:58 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests11 out of 12 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/19 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
NuGetNXPorts1.1.0netfx_loader/ClrLoader.csproj
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.3netfx_loader/ClrLoader.csproj
PyPIcffi>= 1.17pyproject.toml
All dependencies 44

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

RegistryPackageVersionRelation
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.0direct
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.3direct
NuGetNXPorts1.1.0direct
PyPIcffi2.1.1direct
NuGetMicrosoft.NETCore.Platforms1.1.0indirect
NuGetMicrosoft.NETFramework.ReferenceAssemblies.net4611.0.0indirect
NuGetMicrosoft.NETFramework.ReferenceAssemblies.net4611.0.3indirect
NuGetNETStandard.Library2.0.3indirect
PyPIaccessible-pygments0.0.5indirect
PyPIalabaster1.0.0indirect
PyPIbabel2.18.0indirect
PyPIbeautifulsoup44.15.0indirect
PyPIcertifi2026.7.22indirect
PyPIcharset-normalizer3.5.1indirect
PyPIcolorama0.4.6indirect
PyPIdocutils0.22.4indirect
PyPIexceptiongroup1.3.1indirect
PyPIfuro2025.12.19indirect
PyPIidna3.19indirect
PyPIimagesize2.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIjinja23.1.6indirect
PyPImarkupsafe3.0.3indirect
PyPIpackaging26.3indirect
PyPIpluggy1.6.0indirect
PyPIpycparser3.0indirect
PyPIpygments2.21.0indirect
PyPIpytest9.1.1indirect
PyPIrequests2.34.2indirect
PyPIroman-numerals4.1.0indirect
PyPIruff0.16.3indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsoupsieve2.9.2indirect
PyPIsphinx9.1.0indirect
PyPIsphinx-basic-ng1.0.0b2indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItomli2.4.1indirect
PyPItyping-extensions4.16.0indirect
PyPIurllib32.7.0indirect
Dependency advisories 0

Installing pypi:clr_loader@0.3.1 pulls in 2 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 statisticsPyPI.