github-repo-candidate-quality-gate

To filter noisy GitHub repository search results into vetted candidates, apply a deterministic gate sequence checking license, archived status, freshness, fit, and signal to enrich keeps with metadata like full_name, stars, and provenance labels.

A deterministic quality gate for triaging GitHub repos applies fixed sequential filters for license validity, archived status, commit freshness, fit rationale, and traction signals to ensure only recommendation-grade repositories pass through.

Generate rollback-safe reports for maintenance PR workflows by processing GitHub search batches through metadata enrichment and lane-level reporting, producing kept_count, raw_count, and degraded-causes for audit trails.

Yes, you can preserve broad discovery evidence while filtering GitHub repos by applying a gate sequence that retains raw_count metrics and provenance labels alongside kept candidates, ensuring original search scope remains visible.

When triaging GitHub repos for maintenance planning, each kept candidate is enriched with full_name, url, license, pushed_at, archived status, stars, a one-line fit rationale, and a provenance label.

Provenance labels and degraded-causes tracking are needed in GitHub repo triage to support cron reviews and audits by documenting why candidates were kept or filtered, ensuring rollback-safe reporting for maintenance PR workflows.