开发者工具2 weeks ago
RepoMeter — GitHub traffic history that never expires
永久存档GitHub仓库的流量、克隆和来源数据。
@resetnak · X
- Github Repository statistics for opensource projects! Give it a try
完整作品展
技术栈
16 projects
永久存档GitHub仓库的流量、克隆和来源数据。
@resetnak · X
- Github Repository statistics for opensource projects! Give it a try
搜索索引化的开源代码和软件包，包含版本、依赖和漏洞信息。
@Jack_Timonen · X
在Git仓库中存储Markdown文档，无数据库依赖，无厂商锁定。
@alizreim · X
Documentation that lives in your own git repository
发现趋势 GitHub 仓库、初学者议题和 GSoC 组织，寻找开源贡献机会。
@Manixh02 · X
分析开源 GitHub 项目的健康指标、漏洞和质量数据。
Koimiao · V2EX
做了个小工具，可以从各个维度评估一个 GitHub 项目，想请大家拍砖 找开源项目时，我们常常会先看 Star 、README 和最近一次提交。如果你是独立开发者，正在维护自己的开源项目，也想知道怎么让自己项目更健康、被更多人看见，第一步该从哪里做起？ 所以最近我做了一个小项目：TrustOSS http://trustoss.org 输入一个 GitHub 仓库链接，TrustOSS 会把这些公开信号整理成一份可读的仓库健康报告：活跃度、维护情况、社区、文档与成熟度评分；也可以进一步查看漏洞、CI 、真实依赖者、维护者集中度和 Star 异常情况。 想要评估一个开源项目，或者维护自己的开源项目，想知道短板在哪里，都可以直接试试（是免费的！
为开源项目生成的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'
项目管理、文档和测试管理的一体化工作空间。
@klorityx · X
One workspace for project management, documentation, test management & CRM. Enterprise features without enterprise pricing.
ColabWize 审计学术引用并验证作者身份，证明学术工作的真实性。
@clawncore · X
从单一面板管理多个注册商的DNS、SSL、续费和域名所有权。
@itstarun1994 · X
Anythings 是 AI 任务管理器，将语音、截图、邮件等转为智能有序待办清单。
@build_it_lou · X
Anythings - the to do list that keeps itself in order.
粘贴 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
