Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-30 21:22 UTC

infragate / capa

One capabilities.yaml wires skills, tools, rules, sub-agents, MCP servers, and plugins into Cursor, Claude Code, Codex, Windsurf, GitHub Copilot, and 30+ other AI coding agents

TypeScriptNo license detected★ 698 stars⑂ 49 forkssince Feb 2026View on GitHub ↗
KindMCP serverLibraryWeb interfaceCommand-line toolhow this is determined

infragate/capa holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (84/100) and lowest on Sustainability & Governance (42/100). It was last updated today. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

InfragateOrganization
0 followers2 public repossince Jul 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmcapa⚠ Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.0.0.11111241 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
13.8/36Commit cadence20/52 weeks with commits
18/18Commit volume349 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year349
human_commit_share0.95
days_since_last_push0
active_weeks_last_year20
How it's scored
27/27Ships releases50 releases published
36/36Release recencylatest release 13 days ago
27/27Release cadencea release every ~4 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count50
latest_release_tagv1.9.18
releases_from_tagsno
days_since_latest_release13
mean_days_between_releases4

Community & Adoption

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

56Moderate · 17% of overall
How it's scored
46.1/60Stars698 stars
14/25Forks49 forks
0/15Watchers1 watchers
Inputs used
forks49
stars698
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

42Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.4/22.5Commit distributiontop contributor authored 98% of commits
4.1/13.5Contributor breadth3 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.982
How it's scored
36.9/42Issue resolution88% of issues closed
29.7/30PR acceptance96/97 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/23 approved changesets -- score normalized to 0
Inputs used
merged_prs96
open_issues5
closed_issues36
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.878
closed_unmerged_prs1
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
0/25Owner reach0 followers of infragate
5.6/25Track record2 public repos, account ~1 yr old
Inputs used
followers0
owner_typeOrganization
is_verified
owner_logininfragate
public_repos2
account_age_days385
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 1,241 days ago
4/20Version history1 published versions
0/20Not deprecatedcapa: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
Inputs used
packagescapa
ecosystemsnpm
any_deprecatedyes
min_days_since_publish1,241

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests4 out of 5 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://capa.infragate.ai
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicsagentic-workflow, mcp, mcp-server, package-manager, capabilities, skills, mcp-gateway
has_wikino
homepagehttps://capa.infragate.ai
docs_sitehttps://capa.infragate.ai
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-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2/2.5CI-Tests4 out of 5 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/23 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4.5/5SASTSAST tool detected but not run on all commits
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.5Vulnerabilities60 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages40
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 1 resolved dependencies against OSV. 40 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history90 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.947
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingtsconfig.json, web-ui/tsconfig.json
0/10Reproducible environment
10/10Demonstrated agent practice41 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance5 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json, web-ui/tsconfig.json
agent_commit_share0.41
toolchain_manifests
dependency_bot_commit_share0.05
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.8/55Manageable file sizes1/283 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes89,961
source_files_sampled283
oversized_source_files1
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

698GitHub stars
3contributors
349commits, last 12 months
0days since last push
50releases
1bus factor
5open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 49 ⇿
0Stars
49Forks
35Releases

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.

0102030405049332026-032026-052026-07
Major 0Minor 8Patch 27
OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-30 21:22 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
8CI-Tests4 out of 5 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/23 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 26 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
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities60 existing vulnerabilities detected
Direct dependencies 33
RegistryPackageVersion constraintManifest
npm@clack/prompts^1.4.0package.json
npm@iarna/toml^2.2.5package.json
npm@modelcontextprotocol/sdk^1.0.4package.json
npm@radix-ui/react-collapsible^1.1.12package.json
npm@radix-ui/react-dialog^1.1.15package.json
npm@radix-ui/react-dropdown-menu^2.1.16package.json
npm@radix-ui/react-label^2.1.8package.json
npm@radix-ui/react-separator^1.1.8package.json
npm@radix-ui/react-slot^1.2.4package.json
npm@radix-ui/react-tabs^1.1.13package.json
npm@radix-ui/react-tooltip^1.2.8package.json
npm@tanstack/react-query^5.100.9package.json
npmclass-variance-authority^0.7.1package.json
npmclsx^2.1.1package.json
npmcommander^15.0.0package.json
npmdompurify^3.4.3package.json
npmhighlight.js^11.11.1package.json
npmi18next^26.0.10package.json
npmjs-yaml^5.0.0package.json
npmlistr2^10.2.1package.json
npmlucide-react^1.14.0package.json
npmmarked^18.0.3package.json
npmnanoid^5.0.8package.json
npmpicocolors^1.1.1package.json
npmreact^19.2.6package.json
npmreact-dom^19.2.6package.json
npmreact-i18next^17.0.7package.json
npmreact-icons^5.6.0package.json
npmreact-router-dom^7.15.0package.json
npmtailwind-merge^3.5.0package.json
npmxdg-basedir^5.1.0package.json
npmyaml^2.9.0package.json
npmzod^4.4.3package.json
All dependencies 41

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

RegistryPackageVersionRelation
npm@clack/prompts^1.4.0direct
npm@iarna/toml^2.2.5direct
npm@modelcontextprotocol/sdk^1.0.4direct
npm@radix-ui/react-collapsible^1.1.12direct
npm@radix-ui/react-dialog^1.1.15direct
npm@radix-ui/react-dropdown-menu^2.1.16direct
npm@radix-ui/react-label^2.1.8direct
npm@radix-ui/react-separator^1.1.8direct
npm@radix-ui/react-slot^1.2.4direct
npm@radix-ui/react-tabs^1.1.13direct
npm@radix-ui/react-tooltip^1.2.8direct
npm@tanstack/react-query^5.100.9direct
npmclass-variance-authority^0.7.1direct
npmclsx^2.1.1direct
npmcommander^15.0.0direct
npmdompurify^3.4.3direct
npmhighlight.js^11.11.1direct
npmi18next^26.0.10direct
npmjs-yaml^5.0.0direct
npmlistr2^10.2.1direct
npmlucide-react^1.14.0direct
npmmarked^18.0.3direct
npmnanoid^5.0.8direct
npmpicocolors^1.1.1direct
npmreact^19.2.6direct
npmreact-dom^19.2.6direct
npmreact-i18next^17.0.7direct
npmreact-icons^5.6.0direct
npmreact-router-dom^7.15.0direct
npmtailwind-merge^3.5.0direct
npmxdg-basedir^5.1.0direct
npmyaml^2.9.0direct
npmzod^4.4.3direct
npm@biomejs/biome^2.4.15indirect
npm@tailwindcss/cli^4.2.4indirect
npm@types/bunlatestindirect
npm@types/dompurify^3.0.5indirect
npm@types/node^26.0.0indirect
npm@types/react^19.2.14indirect
npm@types/react-dom^19.2.3indirect
npmtailwindcss^4.2.4indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 40 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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

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