Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 05:51 UTC

bobmatnyc / claude-mpm

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

PythonCustom license★ 150 stars⑂ 34 forkssince Jul 2025View on GitHub ↗
KindCommand-line toolLibraryNetwork serviceMCP serverWeb interfacePluginhow this is determined

bobmatnyc/claude-mpm holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (95/100) and lowest on Security (58/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Robert (Masa) MatsuokaPersonal account
60 followers76 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?

89Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 9 days ago
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 4,033 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year4,033
human_commit_share1
days_since_last_push9
active_weeks_last_year47
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 44 days ago
27/27Release cadence — a release every ~2.9 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv6.5.83
releases_from_tagsno
days_since_latest_release44
mean_days_between_releases2.9

Community & Adoption

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

59Moderate · 17% of overall
How it's scored
35.3/60Stars — 150 stars
12.7/25Forks — 34 forks
0/15Watchers — 2 watchers
Inputs used
forks34
stars150
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license 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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateno
How it's scored
54.7/80Monthly downloads — 12,744 downloads/month across npm, pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesclaude-mpm, claude-mpm
dependents—
ecosystemsnpm, pypi
total_downloads—
monthly_downloads12,744
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 factor — 1 contributor(s) cover half of all commits
0.9/22.5Commit distribution — top contributor authored 96% of commits
13.5/13.5Contributor breadth — 14 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.959
How it's scored
42/42Issue resolution — 100% of issues closed
26.7/30PR acceptance — 277/311 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs277
open_issues0
closed_issues649
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs34
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
12.8/25Owner reach — 60 followers of bobmatnyc
25/25Track record — 76 public repos, account ~15 yr old
Inputs used
followers60
owner_typeUser
is_verified—
owner_loginbobmatnyc
public_repos76
account_age_days5,537
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on npm, pypi
35/35Publish recency — latest publish 44 days ago
20/20Version history — 796 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesclaude-mpm, claude-mpm
ecosystemsnpm, pypi
any_deprecatedno
min_days_since_publish44

Engineering Quality

Are baseline engineering and documentation practices in place?

95Exceptional · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .ruff.toml, pyproject.toml ([tool.ruff], [tool.pylint])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 17 out of 18 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://github.com/bobmatnyc/claude-mpm/blob/main/README.md
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsai, claude, cli, mcp, multi-agent, orchestration, plugin, python
has_wikiyes
homepage—
docs_sitehttps://github.com/bobmatnyc/claude-mpm/blob/main/README.md
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 17 out of 18 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/30 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 159 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.2
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
8.8/25Indirect dependencies free of known advisories — 1 affected: extract-zip 2.0.1 (high 8.1)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages114
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the npm:claude-mpm@6.5.83 runtime dependency closure — what installing the published package pulls in — 114 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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md, docs/specs/agents.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.anthropic.com/llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.anthropic.com/llms.txt
legible_history_share1
agent_instruction_filesCLAUDE.md, docs/specs/agents.md
agent_instruction_max_bytes43,276
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .ruff.toml, pyproject.toml ([tool.ruff], [tool.pylint])
11/11Static type checking — pyrightconfig.json, src/claude_mpm/dashboard-svelte/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configspyrightconfig.json, src/claude_mpm/dashboard-svelte/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (pyrightconfig.json, src/claude_mpm/dashboard-svelte/tsconfig.json)
54.3/55Manageable file sizes — 28/2,333 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes964,324
source_files_sampled2,333
oversized_source_files28
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

150GitHub stars
14contributors
4,033commits, last 12 months
9days since last push
100releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 34 ⇿
0Stars
34Forks
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.

01325383422025-092026-032026-09
Major 0Minor 3Patch 97
OpenSSF Scorecard 5.2 / 10
5.2aggregate

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-10 05:51 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests17 out of 18 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/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.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities159 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

Dependency advisories 1

Installing npm:claude-mpm@6.5.83 pulls in 114 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
extract-zip2.0.1indirecthigh2—

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