GitHub force-push to sensitive branch
Jito's assessment for RD-F-108 — scored not_assessed on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
jito-foundation/jito-solana has active normal commit cadence (last commit 2026-04-29 per data cache). No force-push events or unauthorized sensitive-branch pushes detected from available public sources. Data cache confirms github.last_commit_date=2026-04-29 and security_md_present=true. v1-deferred signal; GitHub API monitoring required for automated detection.
Sources #
- GitHubJito Foundation Jito-Solana GitHub Repositoryjito-foundation/jito-solana — last_commit_date: 2026-04-29; security_md_present: true; no force-push reports in public sourcesretrieved 2026-04-29
Methodology #
Detect whether the repository shows a force-push or push to a sensitive branch (main, production tag) from a non-protocol account.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol jito factor RD-F-108 score not_assessed collected_at 2026-04-29 15:50:23