Organization assessment

Beyond individual repositories, inspect.software assesses GitHub organizations — the entities that steward software portfolios. An organization assessment answers a procurement-grade question: is this a maintained, accountable, clearly presented steward, independent of any single repository it owns.

Organization values use the same 1–100 scale and the same rating bands as repositories, computed under the same versioned methodology.

Categories and metrics

Activity & Reach asks whether the repository portfolio is maintained and whether the organization has traction. Governance & Profile asks whether the organization is accountable and clearly presented — the same identity evidence that feeds a repository's stewardship metric.

How portfolio facts are computed

Portfolio measurements are computed over a sample of up to 100 public repositories (the API page cap), ordered by most recent push. For organizations above that size, the sample favors the actively maintained end of the portfolio — stated here because honest methodology includes its sampling rules.

How organization and repository assessments relate

• A repository report embeds its owning account's public profile, which drives the repository's stewardship metric — so organization quality already influences repository values where it should.
• An organization assessment is the aggregate view: one number for the steward across everything it maintains.
• The same missing-data discipline applies throughout: unavailable facts are excluded and weights renormalized, never counted as zero (see the health index).

Improving an organization's assessment

• Keep the portfolio honest: archive repositories that are no longer maintained rather than letting them decay in place — see portfolio activity.
• Complete the organization profile and verify its domain — see profile completeness.

Related: stewardship · methodology versions