GitHub force-push to sensitive branch
EigenLayer'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 #
GitHub repo github.com/Layr-Labs/eigenlayer-contracts is the primary monitored surface. Last commit: 2026-04-07. No public reports of unauthorized force-push or sensitive-branch push incidents. Repository uses release tags for deployment; GitHub API monitoring for unauthorized pushes to main/production branches is implementable. No force-push events identified in publicly available commit history.
Sources #
- Curator noteEigenLayer data cache — github sectiongithub.repo_url: https://github.com/Layr-Labs/eigenlayer-contracts; github.last_commit_date: 2026-04-07 — active, no anomalous push pattern observedretrieved 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 →