# josh-project/josh

Git at scale platform

Repository: https://github.com/josh-project/josh
Canonical: https://ross.abutalabs.com/products/josh
Homepage: https://josh-project.dev
Language: Rust
License: MIT
License Family: permissive
Topics: git, monorepo, workflow, scm
Last push: 2026-08-26T20:39:45+00:00

## Health v2 (maintenance only)
Score: 94/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 83, longevity 100
- inputs: {"age_days": 3736, "days_push": 7, "days_rel": 36, "gap_med": 33, "n_releases_24m": 6}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1915, forks 84 (observed 2026-08-28T04:05:53.672286+00:00)

## What it is
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
- artifact type: service
- maturity: active
- function: version-control, proxy, developer-tools, cli, api-framework
- domain: version-control, developer-tools
- platform: windows, self-hosted, cli
- tags: git, monorepo, git-virtualization, repo-filtering, merge-queue, access-control, rust, scm, devops, automation, linux, macos, docker

## Member repositories
- josh-project/josh (main) score 94

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:53.672286+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:10:23.817153+00:00, confidence not recorded.
  - readme: https://github.com/josh-project/josh (fetched 2026-08-28T04:05:53.672286+00:00, sha 9f6990011f3a)
  - homepage: https://josh-project.dev (fetched 2026-08-29T10:49:37.218529+00:00, sha 36acd76a9821)
  - site_page: https://josh-project.dev/about (fetched 2026-08-29T10:49:37.227758+00:00, sha 8eeb3b7c54df)
  - registry_crates: https://crates.io/api/v1/crates/josh (fetched 2026-08-29T10:49:37.231127+00:00, sha 161227c89d0b)
  - site_page: https://josh-project.dev/faq (fetched 2026-08-29T10:49:37.229613+00:00, sha 4b1d175db20e)
- Data as of 2026-08-30T08:39:29.467469+00:00.