GitHub force-push to sensitive branch
Balancer (v2 + v3)'s assessment for RD-F-108 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
GitHub force-push to sensitive branch | Applicable: Yes — v2 monorepo github.com/balancer/balancer-v2-monorepo; v3 monorepo github.com/balancer/balancer-v3-monorepo | v2 monorepo last commit 2025-12-14 (data cache confirmed). No public reports of unauthorized force-push to main/production branches in the assessment window. v2 monorepo in wind-down posture (last commit 5+ months ago) consistent with Labs wind-down. v3 monorepo still actively maintained (Certora audits Jan 2026, deployment expansions to HyperEVM/Plasma per BIP-862/BIP-874). No anomalous push patterns detected in either repo. | Threshold: Force-push or unauthorized push to main/production branch | Would fire: No
Sources #
- GitHubhttps://github.com/balancer/balancer-v3-monoreporetrieved 2026-05-05
- https://github.com/balancer/balancer-v2-monoreporetrieved 2026-05-05
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 →