[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-81540":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":12,"contributorsCount":12,"subscribersCount":12,"size":12,"stars1d":12,"stars7d":14,"stars30d":14,"stars90d":12,"forks30d":12,"starsTrendScore":12,"compositeScore":15,"rankGlobal":9,"rankLanguage":9,"license":16,"archived":17,"fork":17,"defaultBranch":18,"hasWiki":19,"hasPages":17,"topics":20,"createdAt":9,"pushedAt":9,"updatedAt":21,"readmeContent":22,"aiSummary":23,"trendingCount":12,"starSnapshotCount":12,"syncStatus":24,"lastSyncTime":25,"discoverSource":26},81540,"gitflare","sinameraji\u002Fgitflare","sinameraji","GitHub-shaped developer experience on Cloudflare primitives — Artifacts, Sandboxes, Mesh. Self-host on your own Cloudflare account.",null,"TypeScript",27,0,26,1,40.6,"MIT License",false,"main",true,[],"2026-06-11 04:07:33","\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Flogo.png\" alt=\"GitFlare\" width=\"160\" \u002F>\n\u003C\u002Fp>\n\n\u003Ch1 align=\"center\">GitFlare\u003C\u002Fh1>\n\n\u003Cp align=\"center\">\n  \u003Cstrong>A backup plan for your GitHub repos.\u003C\u002Fstrong>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  Self-host a live mirror on your own Cloudflare account. One command, private by default, open source. Nothing routes through anyone else.\n\u003C\u002Fp>\n\n---\n\n## Roadmap\n\nGitFlare ships in versions. Each one stands alone — if the next one never gets built, the current one is still useful by itself. The grand plan is to move from \"read replica\" all the way to \"fully self-sovereign collaboration on Cloudflare primitives.\" Full design and the reasoning behind each version is in [PLAN.md](.\u002FPLAN.md).\n\n| Version | Status | What it does |\n|---|---|---|\n| **v0.1** | ✅ **shipping — you are here** | **Read replica.** One command mirrors a GitHub repo into your Cloudflare account: Artifacts for git storage, a Worker that takes GitHub webhooks + serves a dashboard, file browsing, README rendering, sync status. If GitHub is down, reads + clones still work. |\n| v0.2 | 🚧 next | **CD that doesn't depend on GitHub.** Push to GitHub → your GitFlare Worker runs `wrangler deploy` against your own account. When GitHub Actions is down, your prod still ships. |\n| v0.3 | 📋 planned | **Generic CI.** A small declarative workflow format that runs tests on Cloudflare Sandboxes (full Linux) or Dynamic Workers (fast JS path). Build cache in R2. Browser Run for E2E. |\n| v0.4 | 📋 planned | **Multi-user teams.** PRs, reviews, comments — native to GitFlare, bidirectionally mirrored to GitHub. Stacked diffs. \"Open PR in sandbox\" one-click ephemeral env. |\n| v0.5 | 📋 planned | **Cross-tenant collaboration via Cloudflare Mesh.** Alice and Bob on separate Cloudflare accounts; private repos served Mesh-only with per-identity policies instead of SSH keys. |\n| v0.6 | 📋 planned | **Public repos + discovery.** A real code browser for the public web, search, forks across accounts. |\n| v1.0 | 📋 someday | **Production-ready, fully open source.** Hardening, polish, multi-region durability. No hosted product, no paid tier — GitFlare stays an MIT CLI you run on your own account. |\n\n## Try it\n\nInstall once:\n\n```bash\nnpm i -g gitflare\n```\n\nThen, from inside any GitHub repo on your machine:\n\n```bash\ngitflare init        # autodetects the GitHub remote from the current directory\n```\n\nOr pass a repo explicitly:\n\n```bash\ngitflare init github.com\u002F\u003Cowner>\u002F\u003Crepo>\n```\n\nThe CLI walks you through a GitHub PAT + a scoped Cloudflare API token (three account-level permissions, all named), shows you exactly what it's about to provision, and waits for confirmation. After that it imports your repo into Artifacts, deploys a Worker on your account, sets secrets, installs a webhook, and prints the dashboard URL. Step-by-step walkthrough with screenshots in [QUICKSTART.md](.\u002FQUICKSTART.md).\n\nGitFlare never sees your code, your token, or your traffic. It's an MIT-licensed CLI; everything it provisions runs on infrastructure you own.\n\n## Contributing\n\nPre-alpha, built in the open, and there's a lot of obvious next work. PRs and issues are welcome — particularly on:\n\n- **v0.2 (CD).** The plumbing for a `.gitflare\u002Fdeploy.yml` workflow that runs on push and shells out to `wrangler deploy`. Sketched in [PLAN.md §4](.\u002FPLAN.md#v02--deploy-without-github-cd).\n- **M5: Cloudflare Access in front of the Worker** so private repos actually stay private. The dashboard is currently public-readable to anyone with the URL.\n- **Syntax highlighting** in the file viewer (Shiki has a Workers-compatible port).\n- **Image proxy** through the Worker so README images render for private repos too (currently we rewrite to GitHub raw URLs, which only works for public repos).\n- **Better empty states \u002F error messages** anywhere in the CLI or dashboard.\n- **Anything in [PLAN.md §8 Open Questions](.\u002FPLAN.md#8-open-questions-to-resolve-before-v01-starts)** you have a strong opinion on.\n\nHow to contribute:\n\n1. Open an issue describing what you want to do (so we don't duplicate work).\n2. Fork, branch, code. The repo is a pnpm workspace; `pnpm install && pnpm -r typecheck && pnpm -r test` should pass.\n3. Open a PR. Small, focused PRs land fastest.\n\nIf you just want to talk through an idea, open a Discussion or DM [@sinameraji](https:\u002F\u002Fgithub.com\u002Fsinameraji).\n\n## How it works (v0.1)\n\n```\ngit push origin main\n        │\n        ▼\n   github.com ──────► webhook ──────► your Worker ──────► Artifacts (in your account)\n                                                                 │\n                                                                 ▼\n                                                       https:\u002F\u002F\u003Crepo>.\u003Cyou>.workers.dev\n                                                       (git clone + read-only web UI)\n```\n\n- Your Worker, your Artifacts repo, your D1, your R2 — all on your Cloudflare account.\n- Cloudflare's free tier + $5\u002Fmonth Workers Paid covers a solo developer.\n- No server in the loop between you and Cloudflare. We don't have an account to log you into.\n\n## Repository layout\n\n```\ngitflare\u002F\n├── PLAN.md              ← the design doc — read this first\n├── README.md            ← you are here\n├── QUICKSTART.md        ← end-to-end provisioning walkthrough\n├── assets\u002F              ← logo, diagrams\n└── packages\u002F\n    ├── cli\u002F             ← the `gitflare` CLI (Node.js, commander + clack)\n    ├── worker\u002F          ← the Cloudflare Worker — sync pipeline + dashboard\n    └── shared\u002F          ← shared TypeScript types\n```\n\n## License\n\n[MIT](.\u002FLICENSE) © Sina Meraji and GitFlare contributors.\n","GitFlare 是一个基于 Cloudflare 基础设施的 GitHub 仓库备份方案。它允许用户通过简单的命令行操作，在自己的 Cloudflare 账户上自托管一个实时镜像，支持私有仓库，默认情况下完全私密且开源。项目利用了 Cloudflare 的 Artifacts 存储、Workers 接收 GitHub Webhook 并提供包括仪表盘、文件浏览及 README 渲染等功能在内的服务。即使 GitHub 不可用时，仍能进行读取和克隆操作。适合需要为代码仓库提供额外安全保障或希望减少对单一平台依赖性的开发者使用。该项目采用 TypeScript 编写，目前处于活跃开发阶段，计划逐步实现从基本的数据复制到完整的多用户协作功能。",2,"2026-06-11 04:05:26","CREATED_QUERY"]