Stars and mentions
Last 30 days, Oct 5 – Nov 3
Package downloads
Top repositories
mavam’s repositories ranked by pull request authors, as on trending.
Contributes to
Repositories outside mavam’s account where mavam opened or reviewed pull requests in the past 365 days.
Who noticed mavam
Everyone who starred or forked mavam’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories mavam owns. Select an award to embed its badge.
- Gold
- 01st place finishes
- Silver
- 02nd place finishes
- Bronze
- 13rd place finishes
- Awarded repositories
- 1Owned by mavam now
Repositories
Ordered by gold, then silver, then bronze.
- stat-cookbookBest: 3rd by stars, 55 stars001
Every award
Top-three finishes of these repositories in completed trending days and weeks, newest first.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
@henriquebastos @Brendon_Arch @pidotdev @executorsh Pi Durable subagents implemented in mavam/pi-agents. Makes your entire agent graph durable. Petrinets can easily built on top since agents can message with each other (also durably). Now I need to look deeper into your awesome stuff!
@badlogicgames doing basically the same with mavam/pi-agents: - spawn an astra reviewer to check the architecture - spawn luna agents to find X, Y, Z - spawn an opus agent to redraw the cover SVG All backed by pi-durable, so subagents survive crashes.
For many months, Pi annoyingly insisted on a light/dark theme duo, with no option at all to disable the machinery that sets its own colors. Thankfully there was mavam/pi-terminal-theme. But I can’t help but feel that this is needlessly complex. Typically a terminal application with a "native" palette maps its colors to terminal colors in a best effort manner. But I understand that it’s quite awkward to map a set of 60 elements to a set of 18 elements. I believe that the contrast problem is better solved on the terminal emulator’s end. kitty has text_fg_override_threshold, Ghostty has minimum-contrast and iTerm2 has a minimum contrast setting as well. This detail is frustratingly missing from the discussion around Pi’s system theme design. I commend the enthusiasm of the survey but it’s important to be aware that some terminals will rewrite your colors anyway. As a concrete example, the base16_transparent theme in Helix is horrendous with most kitty themes I’ve tried. But a sufficiently high minimum contrast setting made it good enough. Incidentally, here Helix demands 76 colors, which sits uncomfortably close to Pi’s stated number despite the fact that Helix has a much less trivial UI. I don’t want every terminal application to be doing its own contrast calculations; I cannot rely on them doing so, thus I will set minimum contrast anyway so I don’t have to think about it. Perhaps there should be a protocol that allows a terminal application to ask for contrast adjustments when it knows it’s using entirely too many colors and needs help.
@championswimmer Love this! Everyone is doing it, including myself 😅 mavam/pi-agents