GitHub force-push to sensitive branch
Concrete'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 #
GitHub force-push/sensitive-branch push: T-09 v2/deferred signal. Applicable — Blueprint-Finance/concrete-earn-v2-bug-bounty is a public GitHub repo; last commit 2026-04-20 (normal commit, not force-push per data cache). GitHub API monitoring not operational. No force-push indicators visible in current data.
Sources #
- GitHubConcrete V2 GitHub repo — last commit 2026-04-20Blueprint-Finance/concrete-earn-v2-bug-bounty last_commit_date 2026-04-20 per data cache — appears normalretrieved 2026-05-17
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 →
rubric_version v1.7.0 protocol concrete factor RD-F-108 score gray collected_at 2026-05-17 14:36:59