Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 16:23 UTC

thisisthepy / torchnative

Run the real PyTorch ecosystem on device, not reimplementing it

Python · RustApache-2.0★ 4 stars⑂ 1 forksince Mar 2025View on GitHub ↗

thisisthepy/torchnative holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Vitality (76/100) and lowest on Security (1/100). It was last updated today. A single contributor accounts for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

thisisthepyOrganization
16 followers64 public repossince Nov 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPItorchnative0.1.0b111,642230 days agopytorchon-deviceedgefederated-learningtest-time-adaptation

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
9/36Commit cadence — 13/52 weeks with commits
18/18Commit volume — 1,405 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year1,405
human_commit_share0.97
days_since_last_push0
active_weeks_last_year13
How it's scored
27/27Ships releases — 1 releases published
36/36Release recency — latest release 48 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagtarget-python-bundle-2026-10
releases_from_tagsno
days_since_latest_release48
mean_days_between_releases—

Community & Adoption

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

34At Risk · 17% of overall
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars4
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
42.9/80Monthly downloads — 1,642 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestorchnative
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,642
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 factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
40.3/42Issue resolution — 96% of issues closed
27/30PR acceptance — 228/253 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs228
open_issues7
closed_issues164
prs_merged_7d55
prs_decided_7d56
prs_merged_30d55
prs_decided_30d56
issue_closed_ratio0.959
closed_unmerged_prs25
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 backing — organization-owned
0/20Verified domain
8.8/25Owner reach — 16 followers of thisisthepy
19.1/25Track record — 64 public repos, account ~3 yr old
Inputs used
followers16
owner_typeOrganization
is_verifiedno
owner_loginthisisthepy
public_repos64
account_age_days1,113

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
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://thisisthepy.org/torchnative/
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsfederated-learning-framework, llm-inference, on-device-ai, test-time-adapatation
has_wikiyes
homepagehttps://thisisthepy.org/torchnative/
docs_sitehttps://thisisthepy.org/torchnative/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesCargo.lock
manifestspyproject.toml, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

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.

49Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
22.5/40Legible commit history — 41 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.423
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — torchnative/rust/executorch_rt/Cargo.toml, torchnative/rust/torch_c/Cargo.toml, torchnative/rust/vendor/candle-core/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifeststorchnative/rust/executorch_rt/Cargo.toml, torchnative/rust/torch_c/Cargo.toml, torchnative/rust/vendor/candle-core/Cargo.toml, torchnative/rust/vendor/candle-kernels/Cargo.toml, torchnative/rust/vendor/candle-metal-kernels/Cargo.toml, torchnative/rust/vulkan_probe/Cargo.toml, torchnative/rust/wasm_probe/Cargo.toml
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
51.8/55Manageable file sizes — 23/397 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes1,789,325
source_files_sampled397
oversized_source_files23
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples, notebooks
Inputs used
example_dirsexamples, notebooks
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

4GitHub stars
1contributors
1,405commits, last 12 months
0days since last push
1releases
1bus factor
7open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:torchnative@0.1.0b11; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/11/21 16:22:09 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks

More detail

Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPIfilelock—pyproject.toml
PyPItyping-extensions>=4.10.0pyproject.toml
PyPIsetuptools>=77.0.3pyproject.toml
PyPIsympy>=1.13.3pyproject.toml
PyPInetworkx>=2.5.1pyproject.toml
PyPIjinja2—pyproject.toml
PyPIfsspec>=0.8.5pyproject.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.