Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 13:56 UTC

microsoft / pxt-microbit

A Blocks / JavaScript code editor for the micro:bit built on Microsoft MakeCode

TypeScript · C++ · JavaScriptCustom license★ 804 stars⑂ 721 forkssince Mar 2016View on GitHub ↗

microsoft/pxt-microbit holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (92/100) and lowest on AI Readiness (68/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

94
overall / 100
Exceptional

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.

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

Ownership

MicrosoftOrganization · verified domain
129,564 followers8,301 public repossince Dec 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmpxt-microbit9.1.14,6401,45464 days agojavascripteducationmicrobit

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 184 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year184
human_commit_share0.99
days_since_last_push2
active_weeks_last_year43
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 21 days ago
27/27Release cadence — a release every ~4.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv9.0.12
releases_from_tagsyes
days_since_latest_release21
mean_days_between_releases4.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?

75Good · 17% of overall
How it's scored
47.1/60Stars — 804 stars
23.8/25Forks — 721 forks
9.9/15Watchers — 61 watchers
Inputs used
forks721
stars804
watchers61
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, travis-ci.org
has_pull_request_templateno
How it's scored
48.9/80Monthly downloads — 4,640 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespxt-microbit
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads4,640
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?

84Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.5/22.5Commit distribution — top contributor authored 49% of commits
13.5/13.5Contributor breadth — 97 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled97
top_contributor_share0.487
How it's scored
38.3/42Issue resolution — 91% of issues closed
27.5/30PR acceptance — 2,350/2,563 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 19/28 approved changesets -- score normalized to 6
Inputs used
merged_prs2,350
open_issues397
closed_issues4,044
prs_merged_7d1
prs_decided_7d1
prs_merged_30d6
prs_decided_30d6
issue_closed_ratio0.911
closed_unmerged_prs213
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
20/20Verified domain
25/25Owner reach — 129,564 followers of microsoft
25/25Track record — 8,301 public repos, account ~12 yr old
Inputs used
followers129,564
owner_typeOrganization
is_verifiedyes
owner_loginmicrosoft
public_repos8,301
account_age_days4,658

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 64 days ago
20/20Version history — 1,454 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespxt-microbit
ecosystemsnpm
any_deprecatedno
min_days_since_publish64

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 26 out of 26 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://makecode.microbit.org
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicstypescript, blockly, microbit, makecode, pxt, code, editor, education
has_wikino
homepagehttps://makecode.microbit.org
docs_sitehttps://makecode.microbit.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

71Good · 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 — 26 out of 26 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
4.5/7.5Code-Review — Found 19/28 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 17 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate7.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
3.9/25Indirect dependencies free of known advisories — 8 affected: adm-zip 0.5.18 (high 7.5), elliptic 6.6.1 (high 7.3), extract-zip 2.0.1 (high 8.1), +5 more
20.7/40No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 246 days ago
Inputs used
sourceosv
advisories34
affected_packages8
assessed_packages642
unassessed_packages0
affected_by_severityhigh 6, moderate 2
direct_affected_packages0
Matched the npm:pxt-microbit@9.1.1 runtime dependency closure — what installing the published package pulls in — 642 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.

68Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 84 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.848
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — clients/winuploader/Microbit.Uploader/CodeTheMicrobit.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — compiler/tsconfig.json, editor/tsconfig.json, fieldeditors/tsconfig.json, libs/blocksprj/tsconfig.json, libs/bluetoothprj/tsconfig.json, libs/tsconfig.json, libs/tsprj/tsconfig.json, sim/tsconfig.json, tests/base/tsconfig.json
0/10Reproducible environment
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configscompiler/tsconfig.json, editor/tsconfig.json, fieldeditors/tsconfig.json, libs/blocksprj/tsconfig.json, libs/bluetoothprj/tsconfig.json, libs/tsconfig.json, libs/tsprj/tsconfig.json, sim/tsconfig.json, tests/base/tsconfig.json
agent_commit_share0.04
toolchain_manifestsclients/winuploader/Microbit.Uploader/CodeTheMicrobit.csproj
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.3/55Manageable file sizes — 2/159 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes131,849
source_files_sampled159
oversized_source_files2
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
Inputs used
example_dirsexamples
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

804GitHub stars
97contributors
184commits, last 12 months
2days since last push
100releases
2bus factor
397open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-03: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 804 stars today.

More detail

Star and fork history 807 ★ / 721 ⇿
807Stars
721Forks
100Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-03. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

02004006008001,000807697452016-042021-062026-09
Major 1Minor 1Patch 98

Each point covers 10 days.

OpenSSF Scorecard 7.4 / 10
7.4aggregate

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-12 13:55 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-Tests26 out of 26 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 19/28 approved changesets -- score normalized to 6
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmpxt-common-packages14.0.2package.json
npmpxt-core13.0.1package.json
All dependencies 13

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

RegistryPackageVersionRelation
npmpxt-common-packages14.0.2direct
npmpxt-core13.0.1direct
npm@types/dom-mediacapture-record1.0.20indirect
npm@types/marked0.3.0indirect
npm@types/node8.10.66indirect
npm@types/react16.4.7indirect
npm@types/react-dom16.0.3indirect
npm@types/web-bluetooth0.0.4indirect
npmless3.13.1indirect
npmreact16.8.3indirect
npmreact-dom16.11.0indirect
npmsemantic-ui-less2.4.1indirect
npmtypescript4.8.3indirect
Dependency advisories 8

Installing npm:pxt-microbit@9.1.1 pulls in 642 packages, direct and transitive: 8 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
adm-zip0.5.18indirecthigh20.6.0
elliptic6.6.1indirecthigh1—
extract-zip2.0.1indirecthigh2—
image-size0.5.5indirecthigh2—
postcss8.5.6indirecthigh48.5.23
serialize-javascript6.0.2indirecthigh27.0.5
dompurify3.3.0indirectmoderate183.4.13
sanitize-html2.17.0indirectmoderate32.17.7

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 — npm.