josh-project/josh
Git at scale platform observed · 2026-08-28
Health v2 · maintenance only
94/100
- Activity 99
- Release rhythm 83
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 33
- age_days: 3736
- days_rel: 36
- days_push: 7
- n_releases_24m: 6
Adoption not part of the score
1915 stars · 84 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Josh (Just One Single History) is a Git-at-scale platform providing fast, reversible Git history transformation so any sub-view of a repository can be presented as an independent repo. It ships a CLI for local partial projections and josh-proxy, a Git HTTP/SSH proxy with on-the-fly history transformation, shared caching, GraphQL APIs, and a cross-forge merge queue.
Use cases
- split a monorepo subfolder into an independent repo with full history
- manage a monorepo without forcing everyone to clone everything
- control access to parts of a codebase for contractors or open source contributors
- check whether a subproject has already been built without checking out the repo
- run a merge queue across multiple forges
- reduce CI rebuild scope by scoping builds to changed sub-views
- synchronize related repositories through a metarepo
When to choose
- your monorepo has grown too large for contributors to clone and build efficiently
- you need per-team or per-project repo views with preserved history and write-back
- you need fine-grained access control over parts of a Git repository
- you want a merge queue that spans multiple code hosts
- you want to erase the monorepo vs polyrepo distinction with dynamic repo boundaries
When to avoid
- you have small repos with no scaling, access control, or CI scope problems
- you need a fully managed SaaS with no self-hosting or proxy infrastructure
- your team relies on tooling that assumes plain unfiltered Git remotes and cannot work through a proxy
- you only need simple submodules or sparse checkout rather than history-preserving projections
Facets
service · maturity active
version-control proxy developer-tools cli api-framework version-control developer-tools windows self-hosted cli git monorepo git-virtualization repo-filtering merge-queue access-control rust scm devops automation linux macos docker
5 sources
- readme: https://github.com/josh-project/josh · fetched 2026-08-28 · 9f6990011f3a
- homepage: https://josh-project.dev · fetched 2026-08-29 · 36acd76a9821
- site_page: https://josh-project.dev/about · fetched 2026-08-29 · 8eeb3b7c54df
- registry_crates: https://crates.io/api/v1/crates/josh · fetched 2026-08-29 · 161227c89d0b
- site_page: https://josh-project.dev/faq · fetched 2026-08-29 · 4b1d175db20e
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| josh-project/josh | main | 94 |
For agents
markdown · JSON · MCP: product_card(name="josh-project/josh")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem