
RepoMeter — GitHub traffic history that never expires
永久存档GitHub仓库的流量、克隆和来源数据。
@resetnak · X
- Github Repository statistics for opensource projects! Give it a try
完整作品展
技术栈
13 projects

永久存档GitHub仓库的流量、克隆和来源数据。
@resetnak · X
- Github Repository statistics for opensource projects! Give it a try

为您的GitHub仓库编写代码的AI开发者。
vpetroff · HN
CobaltCode – Dedicated persistent computer for Codex

发现趋势 GitHub 仓库、初学者议题和 GSoC 组织,寻找开源贡献机会。
@Manixh02 · X

搜索索引化的开源代码和软件包,包含版本、依赖和漏洞信息。
@Jack_Timonen · X

粘贴 GitHub 仓库扫描安全漏洞,自动修复代码问题。
u/Still_Amphibian545 · Reddit
almost launched a side project with my api keys sitting in the repo (a week free gpt 5.6 on us) was about a day from launching a small project when i noticed my openai key was just sitting in a committed file. it had been there for weeks. no idea how i missed it. made me wonder what else was wrong that i couldn't see. turns out for vibecoded stuff it's usually the same handful of things. secrets in the repo, endpoints with no auth, a database with no access rules, no limit on the ex

为开源项目生成的AI文档wiki,每句话都由代码行引用验证。
u/Comprehensive-Bad-43 · Reddit
I got tired of documentation that lies, so I made docs that have to prove every sentence Founder here! Every codebase I have ever joined had the same problem: the docs describe the code as it was six months ago. Nobody updates them, because updating docs is the least rewarding job in software. So I built RepoFold . You connect a GitHub repo and it generates a full wiki, but with one hard rule: every technical claim has to cite the exact file and line numbers it came from. If the AI can'

分析 GitHub 仓库发现付费工作与贡献机会。
@bashops_dev · X
Building BashOps Radar—repository intelligence for developers. Helping developers identify contribution opportunities that can lead to contracts, paid sprints, and long-term work.

扫描GitHub仓库,检测生产就绪度漂移问题并评分。
gojongo · Product Hunt
ReWeaver AI DriftDetector Drift score for any GitHub repo

Surmado 自动代码审查工具,按照团队规范检查 GitHub PR。
u/surmado_rachel · Reddit
We built a cheaper code review tool for small teams We've been working on a code review tool for small teams, solo founders, and vibe coders who want a second set of eyes on every PR without paying Claude-level prices. The idea is simple: Surmado's Scout reviews your PRs against your own standards, not random generic lint rules. You add a STANDARDS.MD file, and on every push Scout gives you: What looks good/What needs work/A short reviewer brief so a human knows where to focus/Feedback

使用硬件认证和OTP保护GitHub拉取请求。
jallmann · HN
> want without a PR process that requires hardware authentication or proof of presence Just curious, what do you use for this? I built OTP Guard [1] a few years ago for exactly this problem, although I haven't seen any alternatives in the space. Does GitHub have something built-in now? The original framing was more "local malware compromising your GitHub account" ... it never occurred to me that the malware could be a LLM. I really should update the page. [1] https://otpguard.com

自动将你的GitHub提交作为卡片每日发布到X。
@manoj_surya_ · X
I just launched 🚀 A Proof of Ship, every day — straight from your GitHub. You already do the hard part: you commit. git-to-x turns that into a designed card and posts it to X every morning. Your timeline finally looks like what you actually are — someone who ships. → 8 card designs, rotating (terminal, heatmap, flame, ticker…) so it never gets stale → weekly + monthly milestone cards — your streak becomes a story worth following → tweet from your CLI / Cursor / Claude Code without leaving your editor → free for 10 days, full access See who else is shipping daily under #proofofship — and join them. It touches your repo, so safe-to-try came first: → open source (AGPL) — audit it or self-host → read-only — we never touch your code This is my first build-in-public tool. I built it for myself, and for anyone tired of switching between shipping and posting about shipping. First 100 get founding lifetime — a permanent number on every card. Try it, tell me

One keyboard for the whole internet. Every cap on it belongs to a single brand: whoever paid the most.
@khizrrr_ · X
the article nails why went viral, but most of the copies chasing that virality missed the actual lesson — people don't want another leaderboard. bet on that: no rank, just claim a key once