GitHub force-push to sensitive branch

Evidence summary #

GitHub force-push signal applicable: public repo github.com/Benqi-fi/BENQI-Smart-Contracts exists. However, repo last commit is 2023-01-11 — stale state. Active development may have moved to private repos, making this signal blind to most current codebase changes. No force-push or anomalous push observed in public repo. Signal is production pipeline signal not yet implemented; GitHub monitor not implemented. The repo staleness itself is a code-security concern (F139) assessed by code-security-analyst, not a live signal finding.

Sources #

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 →