Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 16:07 UTC

bobmatnyc / claude-mpm

Claude Multi-Agent Project Manager — multi-channel orchestration, GitHub-first SDK mode, and plugin system for Claude

PythonCustom license★ 143 stars⑂ 30 forkssince Jul 2025View on GitHub ↗
KindLibraryNetwork serviceMCP serverCommand-line toolWeb interfacePluginhow this is determined

bobmatnyc/claude-mpm holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Security (41/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Robert (Masa) MatsuokaPersonal account
53 followers75 public repossince Jul 20111M Consulting

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

Package ecosystems

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
35.3/36Commit cadence51/52 weeks with commits
18/18Commit volume4,544 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year4,544
human_commit_share
days_since_last_push0
active_weeks_last_year51
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~1.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv6.5.81
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

60Moderate · 17% of overall
How it's scored
34.9/60Stars143 stars
12.2/25Forks30 forks
0/15Watchers2 watchers
Inputs used
forks30
stars143
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
60.1/80Monthly downloads32,254 downloads/month across npm, pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesclaude-mpm, claude-mpm
dependents
ecosystemsnpm, pypi
total_downloads
monthly_downloads32,254
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.9/22.5Commit distributiontop contributor authored 96% of commits
13.5/13.5Contributor breadth13 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled13
top_contributor_share0.959
How it's scored
42/42Issue resolution100% of issues closed
26.7/30PR acceptance263/296 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs263
open_issues0
closed_issues639
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs33
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.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
12.5/25Owner reach53 followers of bobmatnyc
25/25Track record75 public repos, account ~15 yr old
Inputs used
followers53
owner_typeUser
is_verified
owner_loginbobmatnyc
public_repos75
account_age_days5,482
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on npm, pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history794 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesclaude-mpm, claude-mpm
ecosystemsnpm, pypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.ruff.toml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests10 out of 10 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

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicsai, claude, cli, mcp, multi-agent, orchestration, plugin, python
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities98 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.1

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.

79Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, docs/specs/agents.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md, docs/specs/agents.md
agent_instruction_max_bytes43,276
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.ruff.toml
11/11Static type checkingpyrightconfig.json, src/claude_mpm/dashboard-svelte/tsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configspyrightconfig.json, src/claude_mpm/dashboard-svelte/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.
How it's scored
27/45Type-checkable codePython with type-check config (pyrightconfig.json, src/claude_mpm/dashboard-svelte/tsconfig.json)
54.4/55Manageable file sizes27/2,326 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes964,324
source_files_sampled2,326
oversized_source_files27
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

143GitHub stars
13contributors
4,544commits, last 12 months
0days since last push
100releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-07-17 16:07 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 28 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
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities98 existing vulnerabilities detected
Direct dependencies 43
RegistryPackageVersion constraintManifest
npmplaywright^1.55.0package.json
npmpuppeteer^24.34.0package.json
npmreact^18.2.0package.json
npmreact-dom^18.2.0package.json
npmreact-window^1.8.8package.json
npmreact-window-infinite-loader^1.0.9package.json
npmsocket.io-client^4.8.1package.json
PyPIai-trackdown-pytools>=1.4.0pyproject.toml
PyPIpyyaml>=6.0pyproject.toml
PyPIpython-dotenv>=1.0.0pyproject.toml
PyPIclick>=8.0.0pyproject.toml
PyPIpexpect>=4.8.0pyproject.toml
PyPIpsutil>=5.9.0pyproject.toml
PyPIrequests>=2.25.0pyproject.toml
PyPIflask>=3.0.0pyproject.toml
PyPIflask-cors>=4.0.0pyproject.toml
PyPIwatchdog>=3.0.0pyproject.toml
PyPIpython-socketio>=5.14.0pyproject.toml
PyPIaiohttp>=3.9.0pyproject.toml
PyPIaiohttp-cors>=0.7.0,<0.8.0pyproject.toml
PyPIpython-engineio>=4.8.0pyproject.toml
PyPIaiofiles>=23.0.0pyproject.toml
PyPIwebsockets>=12.0pyproject.toml
PyPIpython-frontmatter>=1.0.0pyproject.toml
PyPImistune>=3.0.0pyproject.toml
PyPItree-sitter>=0.21.0pyproject.toml
PyPIijson>=3.2.0pyproject.toml
PyPItoml>=0.10.2pyproject.toml
PyPIpackaging>=21.0pyproject.toml
PyPIpydantic>=2.0.0pyproject.toml
PyPIpydantic-settings>=2.0.0pyproject.toml
PyPIrich>=13.0.0pyproject.toml
PyPIquestionary>=2.0.0pyproject.toml
PyPIpyee>=13.0.0pyproject.toml
PyPIpathspec>=0.11.0pyproject.toml
PyPIfastapi>=0.100.0pyproject.toml
PyPIuvicorn>=0.20.0pyproject.toml
PyPIhttpx>=0.24.0pyproject.toml
PyPIkeyring>=24.0.0pyproject.toml
PyPIcryptography>=41.0.0pyproject.toml
PyPImcp>=1.0.0pyproject.toml
PyPIhuey>=2.5.0pyproject.toml
PyPIcommitizen>=4.13.9pyproject.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.12.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm, PyPI.