Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 04:09 UTC

mobilint / mblt-model-zoo

Mobilint Model Zoo Project

PythonBSD-3-Clause★ 24 stars⑂ 1 forksince Mar 2025View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

mobilint/mblt-model-zoo holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on Community & Adoption (35/100). It was last updated today. 2 contributors account for most of its recent work.

83
overall / 100
Excellent

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.

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

Ownership

Mobilint, Inc.Organization
24 followers25 public repossince Dec 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPImblt-model-zoo2.6.0-400 days agoquantizationnpumodel-zoopre-quantized-modelsinferencemobilintmbltariesregulusqb

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
24.9/36Commit cadence — 36/52 weeks with commits
18/18Commit volume — 135 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_year135
human_commit_share1
days_since_last_push0
active_weeks_last_year36

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 39 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count39
latest_release_tagv2.6.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases5
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?

35Weak · 17% of overall
How it's scored
22.1/60Stars — 24 stars
0/25Forks — 1 forks
0/15Watchers — 2 watchers
Inputs used
forks1
stars24
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
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_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

73Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.4/22.5Commit distribution — top contributor authored 45% of commits
12.2/13.5Contributor breadth — 9 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled9
top_contributor_share0.451
How it's scored
42/42Issue resolution — 100% of issues closed
29.5/30PR acceptance — 124/126 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-Review — Found 12/30 approved changesets -- score normalized to 4
Inputs used
merged_prs124
open_issues0
closed_issues1
prs_merged_7d10
prs_decided_7d10
prs_merged_30d19
prs_decided_30d19
issue_closed_ratio1
closed_unmerged_prs2
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
10.1/25Owner reach — 24 followers of mobilint
21.8/25Track record — 25 public repos, account ~5 yr old
Inputs used
followers24
owner_typeOrganization
is_verifiedno
owner_loginmobilint
public_repos25
account_age_days2,099

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 — 40 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmblt-model-zoo
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.mobilint.com/
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsai-accelerators, edge-ai, quantization, mobilint, computer-vision, quantized-neural-networks, transformer
has_wikiyes
homepagehttps://www.mobilint.com/
docs_sitehttps://www.mobilint.com/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 29 out of 29 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
3/7.5Code-Review — Found 12/30 approved changesets -- score normalized to 4
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no 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
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 — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. 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.

65Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.mobilint.com/llms.txt)
40/40Legible commit history — 88 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.mobilint.com/llms.txt
legible_history_share0.88
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes6,764
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 24 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.24
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
52.7/55Manageable file sizes — 13/313 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes233,305
source_files_sampled313
oversized_source_files13

Key facts

24GitHub stars
9contributors
135commits, last 12 months
0days since last push
39releases
2bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'mblt-model-zoo' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • deps.dev does not index pypi:mblt-model-zoo@2.6.0; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 12/30 approved changesets -- score normalized to 4
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 17
RegistryPackageVersion constraintManifest
PyPImobilint-qb-runtime>=1.4.0pyproject.toml
PyPInumpy>=1.26.0pyproject.toml
PyPItorch>=2.4.1pyproject.toml
PyPIopencv-python>=4.11.0.86pyproject.toml
PyPIpillow>=11.1.0pyproject.toml
PyPIfaster-coco-eval—pyproject.toml
PyPIhuggingface-hub—pyproject.toml
PyPIscipy—pyproject.toml
PyPIrequests>=2.32.0pyproject.toml
PyPIgdown>=5.2.0pyproject.toml
PyPItqdm—pyproject.toml
PyPImblt-tracker>=1.0.1pyproject.toml
PyPIPyYAML—pyproject.toml
PyPImatplotlib—pyproject.toml
PyPIcityscapesScripts—pyproject.toml
PyPImblt-npu-python>=0.1.0pyproject.toml
PyPImblt-vision-python>=0.0.2pyproject.toml
All dependencies 25

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

RegistryPackageVersionRelation
PyPIgdown—direct
PyPImblt-npu-python—direct
PyPImblt-tracker—direct
PyPImblt-vision-python—direct
PyPImobilint-qb-runtime—direct
PyPInumpy—direct
PyPIopencv-python—direct
PyPIpillow—direct
PyPIrequests—direct
PyPItorch—direct
PyPIanyascii—indirect
PyPIdatasets—indirect
PyPIg2p-en—indirect
PyPIg2pkk—indirect
PyPIjamo—indirect
PyPIjiwer—indirect
PyPIlibrosa—indirect
PyPInumba—indirect
PyPIpre-commit—indirect
PyPIpytest—indirect
PyPIpython-mecab-ko—indirect
PyPIqbcompiler—indirect
PyPIsetuptools—indirect
PyPItransformers—indirect
PyPIunidic—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.