Stars and mentions
Last 30 days, Oct 5 – Nov 3
Package downloads
Cumulative recorded downloads · since 2026-04-08
Across 2 known packages in repositories electric-capital owns. Cumulative totals include recorded downloads before the selected range. Missing observations leave gaps; totals may be incomplete. PyPI excludes known mirrors.
Top repositories
electric-capital’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside electric-capital’s account where electric-capital opened or reviewed pull requests in the past 365 days.
Who noticed electric-capital
Everyone who starred or forked electric-capital’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 electric-capital owns. Select an award to embed its badge.
- Gold
- 01st place finishes
- Silver
- 22nd place finishes
- Bronze
- 03rd place finishes
- Awarded repositories
- 1Owned by electric-capital now
Repositories
Ordered by gold, then silver, then bronze.
- open-dev-dataBest: 2nd by PR authors, 67 PR authors020
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
@HeyResearch team shipping non-stop... Proof, merged: github.com/electric-capit%E2%80%A6 @vladtenev @RobinhoodCrypto @JohannKerbrat @arbitrum
@sriramk I'd go further and say you need a harness that watches over what your AI is doing. Otherwise you're asking for trouble. Check out this thing we build for electric: @QuestHarness electric-capital/quest
We just turned on our github discussions page. Come say hi and feel free to ask any questions! github.com/electric-capital/quest/discussions
Privacy is not just about local inference I'm guessing a lot of people here are interested in local models because it means you're not sending all your data up to some cloud inference provider. But what I find weird is that people will go through all this trouble to set up a model and then run a harness basically in yolo mode on top of that. I'm at a small financial firm and when I was trying to figure out how to deploy AI to the company I kept running into this problem. Even if you could run the model locally, if the harness on top allowed the AI to do risky things with sensitive data, then you haven't really solved the privacy/confidentiality problem. Coding-focused harnesses especially tend to have this problem, because they usually assume more liberal permissions and secured environments to run in. We ended up building our own harness because we couldn't find a good solution. It runs on prem, has pluggable inference backends (including local, of course, we're running Qwen3.8 27b 4bit on an ninfer setup), but also has strict categorization of any integration tools that makes it so that the model can access your data, but can't autonomously send it anywhere without your permission. Our ~30 person firm is using it successfully every day, and I thought it might be worth sharing here since many folks here might have the same goals: electric-capital/quest
@sundarpichai @googlecloud Now if you want all this, but self-hosted, true control over inference (including local models), not tied only to google-approved integrations, and open-source, check out Quest: electric-capital/quest
Now if you want all this, but self-hosted, true control over inference (including local models), not tied only to google-approved integrations, and open-source, check out Quest 😉 electric-capital/quest