GitHub force-push to sensitive branch
Hyperlane's assessment for RD-F-108 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
GitHub last commit 2026-05-15 per data cache — active development. No force-push events confirmed in public-accessible GitHub activity. Live GitHub API webhook monitoring for force-push events on hyperlane-xyz/hyperlane-monorepo main branch is not available in static assessment. T-09 phase-2 signal.
Sources #
- GitHubHyperlane Monorepo GitHubHyperlane monorepo — last commit 2026-05-15; active development; no force-push events confirmed via public APIretrieved 2026-05-17
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 hyperlane factor RD-F-108 score gray collected_at 2026-05-16 23:03:56