GitHub force-push to sensitive branch
Maple Finance'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 #
Last commit to maple-labs/maple-core-v2 was 2026-02-19. No public reports of unauthorized force-push or non-protocol-account push to protected branches. No anomaly publicly detected.
Detail #
Threshold: force-push or unauthorized push to main/production-tag branch. Observed: last commit 2026-02-19 (from data-cache github.last_commit_date). No public GitHub security advisory or report of unauthorized push. maple-labs org has standard branch protection expected for a protocol of this maturity (15 audit engagements, 6 firms). Phase-2 signal — GitHub monitoring not live in pipeline.
Sources #
- GitHubhttps://github.com/maple-labs/maple-core-v2retrieved 2026-04-27
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 →