GitHub force-push to sensitive branch
Orca'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 #
GitHub force-push to sensitive branch. Repository orca-so/whirlpools is public. GitHub last commit 2026-05-14 (cache). No force-push incidents documented in public sources. Normal active development commit cadence. No unauthorized pusher events identified. Signal not firing.
Sources #
- GitHubOrca Whirlpools GitHub repo (no FV spec directory found)https://github.com/orca-so/whirlpoolsretrieved 2026-05-16
- Orca cache — GitHub public, recent commit00-data-cache.json sources.github.last_commit_date=2026-05-14; github_private=falseretrieved 2026-05-16
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 orca factor RD-F-108 score green collected_at 2026-05-16 02:39:16