# GitHits > GitHits is the infrastructure layer connecting agents to the open-source ecosystem. Connect your software factory or coding agent to a version-aware index of open-source code, documentation, and package data. Discover, use, debug, and maintain dependencies through one interface. Available through MCP, CLI, and API. Open source powers modern software. GitHits brings source code, documentation, package releases, dependency graphs, and security advisories together in one version-aware index so agents can inspect the versions they use, compare alternatives, and plan changes. If a repository isn't indexed yet, GitHits indexes it on demand, in tens of seconds for small repositories and minutes for larger ones. GitHits indexes public open-source code from package dependencies and repositories into a version-aware code graph. Agents can search code and docs, read exact source files, grep dependencies, inspect package metadata, check vulnerabilities, review changelogs, compare upgrades, and find implementation examples when they need prior art. GitHits is available through a CLI, MCP server, and public API. Connect an agent with a single command — `npx githits@latest init` — which detects your installed agents, configures them to use GitHits, and signs you in. ## When to use GitHits - Use GitHits when an agent needs version-specific public open-source source code, package documentation, dependency metadata, vulnerability context, changelogs, upgrade evidence, or implementation examples. - Use the [GitHits CLI](https://www.npmjs.com/package/githits) for direct commands or its local MCP server over stdio. Run `npx githits@latest init` to configure supported agents. - Use the [remote MCP server](https://mcp.githits.com) over Streamable HTTP when your MCP client supports remote servers. Follow the [authentication documentation](https://docs.githits.com/authentication.md) for OAuth 2.1 with PKCE or headless `GITHITS_API_TOKEN` setup. - Read the [agent documentation index](https://docs.githits.com/llms.txt) or [full Markdown documentation](https://docs.githits.com/llms-full.txt) when you need the complete CLI, MCP, authentication, or tool reference. ## When not to use GitHits - Do not use GitHits as a source for private repositories or private application data; the index covers public open-source code and package context. - Do not use GitHits as a general-purpose application backend. - Never send access tokens, credentials, private source code, or personal data in support requests or agent prompts. ## Get started - [Web app](https://app.githits.com): Sign in and use GitHits in the browser. - [Install GitHits](https://githits.com/init.md): Run `npx githits@latest init` to detect your installed agents, configure them to use GitHits, and sign in. - [Official GitHits CLI on npm](https://www.npmjs.com/package/githits): Published package for the `githits` command and local MCP server. ## Agent access - [Remote MCP server](https://mcp.githits.com): Connect over Streamable HTTP to use GitHits tools from an MCP client. - [GitHits CLI and local MCP server](https://github.com/githits-com/githits-cli): Run GitHits locally over stdio or use the CLI directly. ## Authentication - Normal CLI setup uses OAuth 2.1 with PKCE and Dynamic Client Registration. Tokens are stored in the system keychain by default and refreshed automatically. - Headless and CI environments can authenticate with the `GITHITS_API_TOKEN` environment variable. Never commit or expose the token. - [Authentication documentation](https://docs.githits.com/authentication.md): Manual authentication, headless environments, proxy behavior, and troubleshooting. ## Agent Skills - [GitHits MCP](https://github.com/githits-com/githits-cli/tree/main/skills/githits-mcp): Use GitHits to find source-grounded context across public open-source code, packages, and documentation. - [GitHits onboarding](https://github.com/githits-com/githits-cli/tree/main/skills/githits-onboarding): Set up GitHits safely across supported coding agents. - [GitHits code](https://github.com/githits-com/githits-cli/tree/main/skills/githits-code): Search and inspect version-specific public repository and package source. - [GitHits package](https://github.com/githits-com/githits-cli/tree/main/skills/githits-package): Inspect package metadata, dependencies, vulnerabilities, changelogs, and upgrades. ## Documentation - [Documentation index for agents](https://docs.githits.com/llms.txt): Token-efficient index of GitHits product documentation in Markdown. - [Full Markdown documentation](https://docs.githits.com/llms-full.txt): Complete GitHits product documentation in Markdown. - [Curated landing-site Markdown corpus](https://githits.com/llms-full.txt): Primary GitHits product pages and selected product articles in one file. - [Documentation](https://docs.githits.com/index.md): Product documentation, CLI reference, MCP setup guides, and tool reference in Markdown. - [Public API overview](https://docs.githits.com/api/overview): Get started with the GitHits public API. - [Changelog](https://docs.githits.com/changelog/overview.md): Release notes and product updates in Markdown. ## Core pages - [Homepage](https://githits.com/index.md): Equip your agents to use open source right through one unified interface for code, documentation, examples, and package intelligence. - [The Problem](https://githits.com/the-problem.md): Why agents get stuck when the open-source stack behind your application stays invisible. - [The Solution](https://githits.com/the-solution.md): How agents discover, understand, and evaluate open-source software through one interface. - [Why GitHits](https://githits.com/why-githits.md): How a unified toolkit helps software factories and coding agents work with open source. - [The Builders](https://githits.com/the-builders.md): The team building GitHits and the origin story behind the product. - [The Index](https://githits.com/the-index.md): What the GitHits index currently holds, when the snapshot was taken, and what each figure measures. - [FAQ](https://githits.com/faq.md): Who GitHits is for, how it works alongside your agent, how the index works, private-repo and data privacy guarantees, and open-source license handling. - [Support / Contact](https://githits.com/support.md): Documentation, frequently asked questions, and the GitHits support email. ## Who it's for - [Software Factories](https://githits.com/who-its-for/software-factories.md): Equip your factory's agents to use open source right. One integration for evaluating dependencies, implementing and reviewing integrations, debugging failures, and updating applications. - [Individual developer](https://githits.com/who-its-for/individual-developer.md): Equip your coding agent to use open source right: check version-specific APIs, trace errors into dependencies, and prepare upgrades. - [Open-source maintainers](https://githits.com/who-its-for/open-source-maintainers.md): Make agents use your project right with access to your code, documentation, and package data. Get your repository's GitHits README badge. ## Blog - [Blog index](https://githits.com/blog.md): Selected build notes, case studies, and product thinking about agents and source-grounded context. - [GitHits CLI Launch](https://githits.com/blog/githits-cli.md): Tools for indexed code navigation, package inspection, documentation access, and code examples. - [Connect Your Agents with a Single Command](https://githits.com/blog/connect-your-agents-to-githits-with-a-single-command.md): One init command detects installed agents, configures them to use GitHits, and signs in. - [Code Navigation](https://githits.com/blog/code-navigation-give-your-agent-real-access-to-the-source.md): Search, file listing, source reads, and grep across indexed packages and repositories. - [Package Intelligence](https://githits.com/blog/package-intelligence-vet-a-dependency-before-you-adopt-it.md): License, dependency, vulnerability, changelog, and upgrade-review data before you add a dependency. - [Compare Coding Agents by How They Actually Behave](https://githits.com/blog/compare-coding-agents-by-how-they-actually-behave.md): Use GitHits in the research phase to compare agents by real behavior before cloning a repo. - [Context is King #3: Open-Source Code as Context](https://githits.com/blog/open-source-code-context-for-coding-agents.md): Olli-Pekka Heinisuo on how open-source code becomes useful context for coding agents. ## Case studies - [DuckDB API Migration](https://githits.com/blog/duckdb-api-migration-case-study.md): How GitHits surfaced the DuckDB v1.3.2 source behavior a vanilla agent run missed. - [SQLx 0.9 Safety Migration](https://githits.com/blog/sqlx-querybuilder-safety-case-study.md): How GitHits preserved SQL injection safety while cutting search churn in an SQLx 0.9 migration. - [Pydantic AI Tenant Routing](https://githits.com/blog/pydantic-ai-tenant-routing-case-study.md): How GitHits used current docs and source to resolve a Pydantic AI tool fix while cutting token churn. ## Community - [Wall of Love](https://githits.com/wall-of-love.md): Reviews from developers using GitHits, with links to their original posts. ## Optional - [Terms of Service](https://githits.com/legal/terms-of-service.md): Terms governing use of GitHits services. - [Privacy Policy](https://githits.com/legal/privacy-policy.md): How GitHits collects, uses, and protects personal data. - [Cookie Policy](https://githits.com/legal/cookie-policy.md): Cookies and similar technologies used by GitHits. - [Data Processing Agreement](https://githits.com/legal/data-processing-agreement.md): Contractual terms for processing customer personal data. - [Subprocessor List](https://githits.com/legal/subprocessor-list.md): Third-party subprocessors used to provide GitHits. - [RSS feed](https://githits.com/rss.xml): Blog updates. - [Sitemap](https://githits.com/sitemap-index.xml): Full list of indexable pages.