Public recordExcellent
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 05:05 UTC
tscircuit / core
Create electronics with Typescript and React. Compile Typescript to Circuit JSON
tscircuit/core holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Security (38/100). It was last updated today. 2 contributors account for most of its recent work.
87
overall / 100Software 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.
87
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)
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 73 is calibrated to 87 on the published index scale (record calibration 2026-08-02).
Ownership
tscircuitOrganization
233 followers362 public repossince Aug 2022
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish |
|---|---|---|---|---|---|
| npm | @tscircuit/core | 0.0.1461 | 151,665 | 1,456 | 0 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
95
Development activity
100Exceptional
How it's scored
| 36/36 | Push recency — last push 0 days ago |
| 36/36 | Commit cadence — 52/52 weeks with commits |
| 18/18 | Commit volume — 1,892 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 1,892 |
| human_commit_share | — |
| days_since_last_push | 0 |
| active_weeks_last_year | 52 |
Release discipline
88Excellent
How it's scored
| 16.2/27 | Ships releases — 100 version tags (no GitHub releases) |
| 36/36 | Release recency — latest release 0 days ago |
| 27/27 | Release cadence — a release every ~0.1 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 100 |
| latest_release_tag | v0.0.1461 |
| releases_from_tags | yes |
| days_since_latest_release | 0 |
| mean_days_between_releases | 0.1 |
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?
57
Popularity & adoption
46Weak
How it's scored
| 27.7/60 | Stars — 52 stars |
| 18/25 | Forks — 146 forks |
| 0/15 | Watchers — 2 watchers |
Inputs used
| forks | 146 |
| stars | 52 |
| watchers | 2 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
50Moderate
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 |
Ecosystem adoption (downloads)
86Excellent
How it's scored
| 69.1/80 | Monthly downloads — 151,665 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | @tscircuit/core |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 151,665 |
| 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?
79
Maintainer resilience (bus factor)
62Moderate
How it's scored
| 25.2/54 | Bus factor — 2 contributor(s) cover half of all commits |
| 13.5/22.5 | Commit distribution — top contributor authored 40% of commits |
| 13.5/13.5 | Contributor breadth — 37 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations |
Inputs used
| bus_factor | 2 |
| contributors_sampled | 37 |
| top_contributor_share | 0.401 |
How it's scored
| 40.9/42 | Issue resolution — 97% of issues closed |
| 20.8/30 | PR acceptance — 1,585/2,288 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 4.5/15 | OpenSSF Scorecard: Code-Review — Found 10/30 approved changesets -- score normalized to 3 |
Inputs used
| merged_prs | 1,585 |
| open_issues | 11 |
| closed_issues | 395 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.973 |
| closed_unmerged_prs | 703 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
85Excellent
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 17/25 | Owner reach — 233 followers of tscircuit |
| 20.8/25 | Track record — 362 public repos, account ~3 yr old |
Inputs used
| followers | 233 |
| owner_type | Organization |
| is_verified | — |
| owner_login | tscircuit |
| public_repos | 362 |
| account_age_days | 1,426 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on npm |
| 35/35 | Publish recency — latest publish 0 days ago |
| 20/20 | Version history — 1,456 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | @tscircuit/core |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 0 |
Engineering Quality
Are baseline engineering and documentation practices in place?
86
Engineering practices
84Excellent
How it's scored
| 24/24 | CI workflows — 14 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — biome.json |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
90Excellent
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://tscircuit.com |
| 10/10 | Repository description |
| 10/10 | Topics — 6 topics |
| 0/10 | Wiki |
Inputs used
| topics | hacktoberfest, electronics, electronics-engineering, kicad, kicad-pcb, electronics-as-code |
| has_wiki | no |
| homepage | https://tscircuit.com |
| docs_site | https://tscircuit.com |
| 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?
38
Security posture
38Weak
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 2.5/2.5 | CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 2.2/7.5 | Code-Review — Found 10/30 approved changesets -- score normalized to 3 |
| 2.5/2.5 | Contributors — project has 13 contributing companies or organizations |
| 0/10 | Dangerous-Workflow — dangerous workflow patterns detected |
| 0/7.5 | Dependency-Update-Tool — no 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 2 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 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 |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 15 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 3 |
| scorecard_aggregate | 3.8 |
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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.
74
Agent context & guidance
75Good
How it's scored
| 45/45 | Agent instructions — AGENTS.md, CLAUDE.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 | AGENTS.md, CLAUDE.md |
| agent_instruction_max_bytes | 6,846 |
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
Verify loop (build / test / typecheck)
54Moderate
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — biome.json |
| 11/11 | Static type checking — tsconfig.json |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no data |
| 0/8 | Automated maintenance — no data |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | tsconfig.json |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | — |
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — TypeScript (statically typed) |
| 54.9/55 | Manageable file sizes — 2/1,457 source files over 60KB |
Inputs used
| primary_language | TypeScript |
| largest_source_bytes | 77,937 |
| source_files_sampled | 1,457 |
| oversized_source_files | 2 |
Machine-readable interfaces
100Exceptional
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software |
| 0/20 | MCP server — not applicable to this kind of software |
| 40/40 | Runnable examples — examples |
Inputs used
| example_dirs | examples |
| has_mcp_signal | no |
| 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
52GitHub stars
37contributors
1,892commits, last 12 months
0days since last push
100releases
2bus factor
11open issues
npmpackage ecosystems
More detail
OpenSSF Scorecard 3.8 / 10
3.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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal 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 |
| 10 | CI-Tests | 16 out of 16 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 3 | Code-Review | Found 10/30 approved changesets -- score normalized to 3 |
| 10 | Contributors | project has 13 contributing companies or organizations |
| 0 | Dangerous-Workflow | dangerous workflow patterns detected |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 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 |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Direct dependencies 12
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | @flatten-js/core | ^1.6.2 | package.json |
| npm | @lume/kiwi | ^0.4.3 | package.json |
| npm | calculate-cell-boundaries | ^0.0.13 | package.json |
| npm | calculate-packing | ^0.0.78 | package.json |
| npm | css-select | 5.1.0 | package.json |
| npm | format-si-unit | ^0.0.7 | package.json |
| npm | nanoid | ^5.0.7 | package.json |
| npm | performance-now | ^2.1.0 | package.json |
| npm | react-reconciler | ^0.32.0 | package.json |
| npm | svg-path-commander | ^2.1.11 | package.json |
| npm | transformation-matrix | ^2.16.1 | package.json |
| npm | zod | ^3.25.67 | package.json |
All dependencies 71
Full resolved dependency set from the GitHub dependency graph: 12 direct and 59 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| npm | @flatten-js/core | ^1.6.2 | direct |
| npm | @lume/kiwi | ^0.4.3 | direct |
| npm | calculate-cell-boundaries | ^0.0.13 | direct |
| npm | calculate-packing | ^0.0.78 | direct |
| npm | css-select | 5.1.0 | direct |
| npm | format-si-unit | ^0.0.7 | direct |
| npm | nanoid | ^5.0.7 | direct |
| npm | performance-now | ^2.1.0 | direct |
| npm | react-reconciler | ^0.32.0 | direct |
| npm | svg-path-commander | ^2.1.11 | direct |
| npm | transformation-matrix | ^2.16.1 | direct |
| npm | zod | ^3.25.67 | direct |
| npm | @biomejs/biome | ^1.8.3 | indirect |
| npm | @resvg/resvg-js | ^2.6.2 | indirect |
| npm | @tscircuit/alphabet | 0.0.25 | indirect |
| npm | @tscircuit/capacity-autorouter | ^0.0.670 | indirect |
| npm | @tscircuit/checks | 0.0.145 | indirect |
| npm | @tscircuit/circuit-json-util | ^0.0.97 | indirect |
| npm | @tscircuit/common | ^0.0.20 | indirect |
| npm | @tscircuit/copper-pour-solver | 0.0.39 | indirect |
| npm | @tscircuit/footprinter | ^0.0.371 | indirect |
| npm | @tscircuit/image-utils | ^0.0.8 | indirect |
| npm | @tscircuit/infer-cable-insertion-point | ^0.0.2 | indirect |
| npm | @tscircuit/infgrid-ijump-astar | ^0.0.35 | indirect |
| npm | @tscircuit/krt-wasm | ^0.1.1 | indirect |
| npm | @tscircuit/log-soup | ^1.0.2 | indirect |
| npm | @tscircuit/matchpack | ^0.0.38 | indirect |
| npm | @tscircuit/math-utils | ^0.0.36 | indirect |
| npm | @tscircuit/miniflex | ^0.0.4 | indirect |
| npm | @tscircuit/ngspice-spice-engine | ^0.0.19 | indirect |
| npm | @tscircuit/props | ^0.0.583 | indirect |
| npm | @tscircuit/schematic-match-adapt | ^0.0.18 | indirect |
| npm | @tscircuit/schematic-trace-solver | ^0.0.101 | indirect |
| npm | @tscircuit/solver-utils | ^0.0.16 | indirect |
| npm | @tscircuit/soup-util | ^0.0.41 | indirect |
| npm | @types/bun | ^1.2.16 | indirect |
| npm | @types/debug | ^4.1.12 | indirect |
| npm | @types/react | ^19.1.8 | indirect |
| npm | @types/react-dom | ^19.1.6 | indirect |
| npm | @types/react-reconciler | ^0.28.9 | indirect |
| npm | bpc-graph | ^0.0.57 | indirect |
| npm | bun-match-svg | 0.0.12 | indirect |
| npm | calculate-elbow | ^0.0.12 | indirect |
| npm | chokidar-cli | ^3.0.0 | indirect |
| npm | circuit-json | ^0.0.450 | indirect |
| npm | circuit-json-to-bpc | ^0.0.13 | indirect |
| npm | circuit-json-to-connectivity-map | ^0.0.23 | indirect |
| npm | circuit-json-to-gltf | ^0.0.105 | indirect |
| npm | circuit-json-to-spice | ^0.0.43 | indirect |
| npm | circuit-to-svg | ^0.0.387 | indirect |
| npm | concurrently | ^9.1.2 | indirect |
| npm | connectivity-map | ^1.0.0 | indirect |
| npm | debug | ^4.3.6 | indirect |
| npm | flatbush | ^4.5.0 | indirect |
| npm | graphics-debug | ^0.0.95 | indirect |
| npm | howfat | ^0.3.8 | indirect |
| npm | kicad-to-circuit-json | ^0.0.113 | indirect |
| npm | kicadts | ^0.0.51 | indirect |
| npm | live-server | ^1.2.2 | indirect |
| npm | looks-same | ^9.0.1 | indirect |
| npm | minicssgrid | ^0.0.9 | indirect |
| npm | pkg-pr-new | ^0.0.37 | indirect |
| npm | poppygl | ^0.0.25 | indirect |
| npm | react | ^19.1.0 | indirect |
| npm | react-dom | ^19.1.0 | indirect |
| npm | schematic-symbols | ^0.0.232 | indirect |
| npm | spicets | ^0.0.2 | indirect |
| npm | spicey | ^0.0.14 | indirect |
| npm | stack-svgs | ^0.0.1 | indirect |
| npm | ts-expect | ^1.3.0 | indirect |
| npm | tsup | ^8.2.4 | 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.11.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — npm.