Josverl / micropython-stubs
Stubs of most MicroPython ports, boards and versions to make writing code that much simpler.
Josverl/micropython-stubs holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (96/100) and lowest on Security (45/100). It was last updated today. A single contributor accounts for most of its recent work.
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.
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 67 is calibrated to 78 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 36/36 | Push recency — last push 0 days ago |
| 35.3/36 | Commit cadence — 51/52 weeks with commits |
| 18/18 | Commit volume — 674 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 674 |
| human_commit_share | — |
| days_since_last_push | 0 |
| active_weeks_last_year | 51 |
Release discipline
How it's scored
| 27/27 | Ships releases — 14 releases published |
| 36/36 | Release recency — latest release 53 days ago |
| 19.8/27 | Release cadence — a release every ~94.4 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 14 |
| latest_release_tag | setup-stubs_v0.1.28 |
| releases_from_tags | no |
| days_since_latest_release | 53 |
| mean_days_between_releases | 94.4 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 40.4/60 | Stars — 311 stars |
| 12.2/25 | Forks — 30 forks |
| 3.3/15 | Watchers — 5 watchers |
Inputs used
| forks | 30 |
| stars | 311 |
| watchers | 5 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0.7/22.5 | Commit distribution — top contributor authored 97% of commits |
| 13.5/13.5 | Contributor breadth — 11 contributors |
| 3/10 | OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 11 |
| top_contributor_share | 0.97 |
Issue & PR responsiveness
How it's scored
| 34.2/42 | Issue resolution — 82% of issues closed |
| 14.9/30 | PR acceptance — 357/720 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 357 |
| open_issues | 29 |
| closed_issues | 128 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.815 |
| closed_unmerged_prs | 363 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Ownership & stewardship
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 13.4/25 | Owner reach — 72 followers of Josverl |
| 25/25 | Track record — 245 public repos, account ~14 yr old |
Inputs used
| followers | 72 |
| owner_type | User |
| is_verified | — |
| owner_login | Josverl |
| public_repos | 245 |
| account_age_days | 5,452 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 24/24 | CI workflows — 13 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .pylintrc |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://micropython-stubs.readthedocs.io |
| 10/10 | Repository description |
| 10/10 | Topics — 13 topics |
| 10/10 | Wiki |
Inputs used
| topics | micropython, vscode, type-checking, static-typing, mypy-stubs, pyright, pylance, pylint, pycharm-ide, type-stubs, awesome-micropython, mypy, pyscript |
| has_wiki | yes |
| homepage | https://micropython-stubs.readthedocs.io |
| docs_site | https://micropython-stubs.readthedocs.io |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
| 0.8/2.5 | Contributors — project has 1 contributing companies or organizations -- score normalized to 3 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 1/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2 |
| 0/5 | SAST — no SAST tool detected |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 3.8/7.5 | Vulnerabilities — 5 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 15 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 3 |
| scorecard_aggregate | 4.5 |
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.
Agent context & guidance
How it's scored
| 45/45 | Agent instructions — .github/copilot-instructions.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | .github/copilot-instructions.md |
| agent_instruction_max_bytes | 10,363 |
Verify loop (build / test / typecheck)
How it's scored
| 18/18 | One-command bootstrap — docs/Makefile, justfile |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .pylintrc |
| 11/11 | Static type checking — publish/micropython-stdlib-stubs/pyrightconfig.json |
| 10/10 | Reproducible environment — devcontainer, Dockerfile |
| 0/10 | Demonstrated agent practice — no data |
| 5/8 | Automated maintenance — dependency automation configured, none observed in the sampled commits |
| 2/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | yes |
| typed_language | no |
| bootstrap_files | docs/Makefile, justfile |
| has_devcontainer | yes |
| has_linter_config | yes |
| typecheck_configs | publish/micropython-stdlib-stubs/pyrightconfig.json |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 27/45 | Type-checkable code — Python with type-check config (publish/micropython-stdlib-stubs/pyrightconfig.json) |
| 55/55 | Manageable file sizes — 8/17,152 source files over 60KB |
Inputs used
| primary_language | Python |
| largest_source_bytes | 869,838 |
| source_files_sampled | 17,152 |
| oversized_source_files | 8 |
Machine-readable interfaces
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software |
| 20/20 | MCP server |
| 40/40 | Runnable examples — examples, notebooks, samples |
Inputs used
| example_dirs | examples, notebooks, samples |
| has_mcp_signal | yes |
| api_schema_files | — |
| interfaces_expected_of | — |
Key facts
Data collection warnings
- File tree truncated by GitHub API; file-based signals may be incomplete
- Could not fetch pypi package 'micropython-stubs' from its registry
More detail
OpenSSF Scorecard 4.5 / 10
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| n/a | CI-Tests | no pull request found |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/30 approved changesets -- score normalized to 0 |
| 3 | Contributors | project has 1 contributing companies or organizations -- score normalized to 3 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 2 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 2 |
| 0 | SAST | no SAST tool detected |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 5 | Vulnerabilities | 5 existing vulnerabilities detected |
All dependencies 13
Full resolved dependency set from the GitHub dependency graph: 0 direct and 13 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| PyPI | google-cloud-bigquery | — | indirect |
| PyPI | jinja2 | — | indirect |
| PyPI | micropython-stdlib-stubs | — | indirect |
| PyPI | micropython-stubber | — | indirect |
| PyPI | mpflash | — | indirect |
| PyPI | myst-parser | — | indirect |
| PyPI | pandas | — | indirect |
| PyPI | pyright | — | indirect |
| PyPI | python | — | indirect |
| PyPI | sphinx | — | indirect |
| PyPI | sphinx-autoapi | — | indirect |
| PyPI | sphinx-rtd-theme | — | indirect |
| PyPI | sphinxcontrib-mermaid | — | indirect |
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.
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.15.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics.