Commit timezone consistent with stated geography
Beefy Finance's assessment for RD-F-119 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
GitHub API returns commit timestamps in UTC (stripped of local timezone offsets per GitHub documented behavior). The observed commit hour distribution (07:00-23:00 UTC) across the 26 recent beefy-contracts commits is a 16-hour window too wide to support any geographic inference. Beefy has not publicly stated a team geography. Raw git-log output with author timezone offsets would be needed for this factor — not obtainable via WebFetch. Factor cannot be assessed reliably with available tooling.
Sources #
- GitHubbeefy-contracts commits APIapi.github.com/repos/beefyfinance/beefy-contracts/commits?per_page=30 — UTC timestamps; local tz not exposedretrieved 2026-05-16
Methodology #
Determine whether the distribution of commit hours in the repo is consistent with the team's publicly stated geography (anomaly flag for DPRK-precursor pattern).
See the full factor methodology and distribution across all protocols →