GitHub force-push to sensitive branch
Veda (BoringVault)'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 #
Post-v1 signal requiring GitHub monitoring infrastructure. Veda-Labs/boring-vault is the canonical repo (last commit 2026-05-15 per data cache). No force-push or sensitive-branch compromise publicly reported. GitHub API monitoring not deployed.
Sources #
- GitHubVeda-Labs/boring-vault GitHub repositoryVeda-Labs/boring-vault: last_commit_date=2026-05-15; no force-push incidents publicly reportedretrieved 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 veda factor RD-F-108 score gray collected_at 2026-05-17 12:41:22