GitHub force-push to sensitive branch
deBridge'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 #
**Phase:** v1 deferred (P2; requires GitHub permissioned access per protocol) **Applicable:** Yes — debridge-finance GitHub org has active repos with protocol-critical code (debridge-contracts-v1, dln-contracts, debridge-launcher). **Current posture:** GitHub API monitoring not configured for this assessment. No public report of unauthorized force-push on deBridge repos. **Would fire today:** Gray — not assessable without GitHub monitoring. **Source:** https://github.com/debridge-finance
Sources #
- GitHubhttps://github.com/debridge-financeretrieved 2026-04-28
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 →