CLI deps
Dependency repository branches needed by the configured CLI lines.
Source commits, scope, and interpretation
Inputs are pinned CLI lockfiles and workspace manifests, including runtime and development dependencies, direct and transitive, and workspace testing/linting requirements.
Template-oss itself stays in scope. Transitives reachable only through template-oss are excluded; dependencies with another path are retained. Repository ownership is canonical, not inferred from package names.
Existing branches match actual package names and majors in branch manifests. Potential gaps lists required branch names without a matching maintenance branch. Upgrades or other release practices may address a requirement instead.
CI badges summarize GitHub check runs and commit statuses for the exact pinned commit, collected separately from the dependency snapshot. They are not a branch-protection or release-readiness assessment.
Version indicators check whether the highest stable published version in each required package major is integrated. The newest configured CLI line also checks the highest stable published version across all majors, including majors the CLI has not yet integrated. These use registry evidence collected by CI, not branch HEADs or browser-side registry lookups.
A checkmark means the published version is present at least once; older copies can still be required. Monorepo indicators cover every package in the grouped branch. Missing versions do not establish upgrade compatibility.
Version filters use only the selected CLI line, or match any CLI when all lines are selected. Not latest in line includes mixed copies of a package major. Unavailable publication data is not classified as current or outdated.
(branch) required line
vN dev-only
release/vN required branch not found
Unmarked usage is runtime; only dev-only usage is labeled.
CI badges link to checks for the pinned commit.
✓ Latest integrated; ↑ version missing not integrated in the collected CLI inputs.