Steven Gonsalvez

Software Engineer

CEREBRO

machine-read, publicly sourced

|profiled from public GitHub activity

CEREBRO developer

mvanhorn

Pushed 566 times across 184 repositories on 72 active days in the 90 days to 2026-09-06.

Public push activity

  • last 7 daysNo public push activity in the last 7 days.
  • last 30 daysPushed 58 times across 33 repositories on 15 active days in the 30 days to 2026-09-06.
  • last 90 daysPushed 566 times across 184 repositories on 72 active days in the 90 days to 2026-09-06.

Active days per window

13 weeks of public push counts, oldest first; lowest 0, highest 100.

13 weeks of public push counts, oldest first; lowest 0, highest 100.

last 7 days
0
last 30 days
15
last 90 days
72

What a push is

A push is one GitHub PushEvent: a single publication of one or more commits to a branch. It is not a commit count, and the public event feed under-counts pull requests, issues and stars since mid-2025, so these numbers describe push activity only.

Automated-activity shapes

An automated-activity shape (mass_self_repo) matched this account's public push pattern and was cleared by e01-fixer on 2026-08-26.

  • 184 distinct repos, 4 not owned (ratio 0.0217), 7.86 pushes per active day

Repositories

Seen in CEREBRO signals

10 signals in the vault put this login in the pool. The GitHub links in them point at addyosmani/agent-skills, affaan-m/ECC, agavra/tuicr, agentscope-ai/QwenPaw, AlexsJones/llmfit, alibaba/page-agent, bytedance/deer-flow, chopratejas/headroom, ChromeDevTools/chrome-devtools-mcp and mvanhorn/last30days-skill.

Also reached the pool through the fanout lane.

If this page is about you and you would rather it were not

If you ask to be removed, this site no longer generates your developer profile, and the pages that are already live come down on the next build. What it cannot do is erase public git history, the GH Archive replica of the public event feed these numbers are derived from, search-engine or Wayback caches, or copies anyone has already cloned. Removal here covers the developer profile page and the developer index entry; where this archive cites public writing by that person as a signal, that citation is a separate record with its own removal path, and it is not covered by this request.

To be removed, open an issue on the pipeline's public repository naming the GitHub login you want taken down. You do not have to give a reason, and none is recorded: the list this site keeps holds the login, the date, how the request arrived and who wrote it down, and nothing about you.

The site rebuilds from a fresh clone of the archive every morning at 07:00, so a removal recorded today is live by the next morning at the latest. An urgent removal is rebuilt the same day by triggering a deploy by hand.

Open a removal request ↗