GitHub force-push to sensitive branch
OpenEden'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. Applicable: github.com/OpenEdenHQ/openeden.vault.audit is public (8 commits total, last commit 2025-09-08). GitHub API monitoring not wired. No public force-push event observed. Low commit velocity (8 total commits) reduces baseline noise.
Sources #
- GitHubOpenEden vault audit repogithub.com/OpenEdenHQ/openeden.vault.audit — 8 total commits, last commit 2025-09-08; no force-push event observable through public GitHubretrieved 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 openeden factor RD-F-108 score gray collected_at 2026-05-16 10:11:45