GET /experimental/orgs/{orgId}/home-summary

The trailing window the activity figures below are measured over, and which their previous counts compare against. installs is the exception: it is measured over the same number of days but ends on installsThrough, because installs are read from a nightly snapshot that never covers today.

Org members who joined during the window, and during the equally long window before it.

Registry versions published from this org over the window. Counts plugins, not the skills inside them. series carries one point per day with zeros included.

Installs of plugins this org published, from the nightly PostHog snapshot, over the window ending window.installsThrough. Counts deliberate installs only — a CLI auto-sync re-install is not one. mostInstalled below is the same measure broken out per plugin, so its rows sum to a subset of this total. Scoped to the workspaces the caller can see, like publishes. Null means the snapshot has never completed a run (a fresh deployment, or a worker with no PostHog credentials); it is never a request-time failure, since this endpoint makes no PostHog call. Zero would be the wrong answer there, because it would assert nobody installed anything.

The org Context collection bucketed by review quality. Read from the same context model the org Context page and the Total context figure use, over the same source scope (visible workspaces plus org-owned SCM accounts) and the same family de-duplication, so the four bands partition that collection and total equals the org Context page's meta.total for the same caller. The bands are that page's filter[score] bands, so each one addresses exactly the rows the page lists when filtered to it. These totals are still scoped differently to avgQuality and belowBarCount above, which come from the per-workspace scan summaries.

The org's most-installed plugins over the same trailing window and from the same nightly PostHog snapshot as installs, ranked most-installed first. installs counts deliberate installs only (a CLI auto-sync re-install is not one), so this panel agrees with the installs card beside it rather than with the cumulative registry download counter. Scoped to the workspaces the caller can see, and measured over the window ending window.installsThrough; empty when no snapshot has ever completed or nothing was installed in the window.

The SCM provider whose most recent scan failed, so a client can point the user at the integration to check. Non-null only when scanStatus is failed. Identifies the provider only: the account name and the underlying error are deliberately not exposed.