Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 13:57 UTC

ahujasid / mcp-for-blender

Community plugin to control Blender 3D with any LLM of your choice

PythonMIT★ 28,943 stars⑂ 2,664 forkssince Mar 2025View on GitHub ↗
KindCommand-line toolMCP serverhow this is determined

ahujasid/mcp-for-blender holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (76/100) and lowest on Security (43/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

51
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.

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

Ownership

ahujasidPersonal account
741 followers16 public repossince Apr 2015

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPImcp-for-blenderpoints to another repo — not scored2.0.0-42 days ago

Metrics by category

Vitality

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

46Weak · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
12.5/36Commit cadence — 18/52 weeks with commits
17.5/18Commit volume — 88 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year88
human_commit_share1
days_since_last_push2
active_weeks_last_year18
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

76Good · 17% of overall
How it's scored
60/60Stars — 28,943 stars
25/25Forks — 2,664 forks
12.8/15Watchers — 203 watchers
Inputs used
forks2,664
stars28,943
watchers203
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.4/22.5Commit distribution — top contributor authored 67% of commits
13.5/13.5Contributor breadth — 39 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled39
top_contributor_share0.673
How it's scored
37.2/42Issue resolution — 89% of issues closed
10.8/30PR acceptance — 52/144 decided PRs merged
7.6/13Newcomer PR acceptance — 7/12 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 7/30 approved changesets -- score normalized to 2
Inputs used
merged_prs52
open_issues20
closed_issues156
prs_merged_7d4
prs_decided_7d9
prs_merged_30d8
prs_decided_30d15
issue_closed_ratio0.886
closed_unmerged_prs92
first_time_authors_30d11
first_time_prs_merged_30d7
first_time_prs_decided_30d12
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
20.6/25Owner reach — 741 followers of ahujasid
21/25Track record — 16 public repos, account ~11 yr old
Inputs used
followers741
owner_typeUser
is_verified—
owner_loginahujasid
public_repos16
account_age_days4,183
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 7 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://mcp-for-blender.com/
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topics3d-modeling, ai, blender, blender-addon, claude, generative-ai, llm, mcp, model-context-protocol, python, blender-mcp
has_wikiyes
homepagehttps://mcp-for-blender.com/
docs_sitehttps://mcp-for-blender.com/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

43Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 7/30 approved changesets -- score normalized to 2
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
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 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.9
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages29
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:mcp-for-blender@2.0.0 runtime dependency closure — what installing the published package pulls in — 29 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://mcp-for-blender.com/llms.txt)
36.3/40Legible commit history — 68 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://mcp-for-blender.com/llms.txt
legible_history_share0.68
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 6 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
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
48.7/55Manageable file sizes — 3/26 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes197,042
source_files_sampled26
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

28,943GitHub stars
39contributors
88commits, last 12 months
2days since last push
0releases
1bus factor
20open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 13 authors (cap 12)
  • pypi package 'mcp-for-blender' points at a different repository (https://github.com/ahujasid/blender-mcp); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 2,664 ⇿
0Stars
2,664Forks

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.

1,5001,7502,0002,2502,5002,7502,664242026-032026-062026-09
OpenSSF Scorecard 2.9 / 10
2.9aggregate

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-18 13:56 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
0CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 7/30 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
n/aToken-PermissionsNo tokens found
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
PyPImcp>=1.9.0,<2pyproject.toml
PyPIhttpx>=0.27.0pyproject.toml
All dependencies 36

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

RegistryPackageVersionRelation
PyPIhttpx0.28.1direct
PyPImcp1.29.0direct
PyPIannotated-types0.7.0indirect
PyPIanyio4.8.0indirect
PyPIattrs26.1.0indirect
PyPIcertifi2025.1.31indirect
PyPIcffi2.1.1indirect
PyPIclick8.1.8indirect
PyPIcolorama0.4.6indirect
PyPIcryptography50.0.0indirect
PyPIexceptiongroup1.2.2indirect
PyPIh110.14.0indirect
PyPIhttpcore1.0.7indirect
PyPIhttpx-sse0.4.0indirect
PyPIidna3.10indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPImcp-for-blender2.0.0indirect
PyPIpycparser3.0indirect
PyPIpydantic2.12.3indirect
PyPIpydantic-core2.41.4indirect
PyPIpydantic-settings2.8.1indirect
PyPIpyjwt2.13.0indirect
PyPIpython-dotenv1.0.1indirect
PyPIpython-multipart0.0.32indirect
PyPIpywin32312indirect
PyPIreferencing0.37.0indirect
PyPIrpds-py0.30.0indirect
PyPIrpds-py2026.6.3indirect
PyPIsniffio1.3.1indirect
PyPIsse-starlette2.2.1indirect
PyPIstarlette0.46.0indirect
PyPIstarlette1.6.0indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPIuvicorn0.34.0indirect
Dependency advisories 0

Installing pypi:mcp-for-blender@2.0.0 pulls in 29 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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