Built with Astro, hosted on Azure Front Door / Azure CDN behind Cloudflare. Domain registered in 2026.
githits.dev is built with Astro, hosted on Azure Front Door / Azure CDN behind Cloudflare. It measures traffic with Ahrefs Web Analytics.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| 7.2.0 | 9 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 9 Nov 2026 | |
| CDN & Hosting3 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
| Reviews, Ratings & Social Proof1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
smtp.google.comnaya.ns.cloudflare.comgarret.ns.cloudflare.comgoogle-site-verification=rAXqRAYfdnLtkLoXYEnYTa8GyrqXmcLFacPgyIvh3fIv=spf1 include:_spf.google.com ~allv=DMARC1; p=none; rua=mailto:dmarc@githits.dev; pct=100User-agent: * Disallow: Content-Signal: search=yes, ai-input=yes, ai-train=yes Sitemap: https://githits.com/sitemap-index.xml
# GitHits > Equip your agents to use open source right. Discover, evaluate, integrate, and maintain open-source software through one interface. GitHits equips software factories and coding agents to build on the open-source ecosystem. Find existing solutions, understand how they work, choose components, and use them throughout development. Build new applications, maintain existing systems, and modernize older software with access to the code and knowledge behind them. GitHits brings public source code, documentation, and package data together in a version-aware index. Agents search and read repositories, explore how projects fit together, compare releases, and learn from implementations across the ecosystem. Connect through CLI, MCP, or the REST API. ## What agents do with GitHits - **Discover existing solutions:** Find projects, approaches, and implementations to build on across open source. - **Understand how software works:** Explore source code, architecture, documentation, and relationships across projects. - **Evaluate components:** Compare capabilities, releases, licenses, dependencies, and security information to choose what fits your application. - **Build and integrate:** Apply what other projects provide and how they work during planning, design, implementation, and code review. - **Debug and maintain:** Investigate behavior, follow changes across versions, and prepare upgrades and migrations. Retrieve source, documentation, and package information directly, or delegate investigations to GitHits research. Generate implementation examples from how other open-source projects solve a problem. Follow source references to continue exploring. ## Build GitHits into your software factory Equip your agents through CLI or MCP, or embed the REST API in your development workflow. Connect the same open-source ecosystem to agents that plan, build, review, debug, and maintain your applications. Use the API to choose what each agent retrieves, shape the information it receives, and integrate GitHits into your own product experience. ## Start with the GitHits CLI Run `npx githits@latest init` to detect your installed agents, configure them to use GitHits, and sign in. Use the CLI directly, through agent skills, or as a local MCP server. - [Install GitHits](https://githits.com/init.md): Set up GitHits in your coding environment. - [Official GitHits CLI on npm](https://www.npmjs.com/package/githits): Install the `githits` command and local MCP server. - [GitHits CLI repository](https://github.com/githits-com/githits-cli): Find CLI releases, source code, and agent skills. ## Connect on your platform Use a plugin or connector instead of the CLI's MCP setup in the same agent. Do not enable both together. To add skills alongside a plugin or connector without configuring another MCP connection, install only the skills: ```bash npx skills add githits-com/githits-cli ``` - [Claude connector](https://claude.ai/directory/githits): Connect GitHits to Claude. - [ChatGPT plugin](https://chatgpt.com/plugins/plugin_asdk_app_6ae059be511481918e3573fb5885dbb8): Add GitHits to ChatGPT. - [Cursor plugin](https://cursor.com/marketplace/githits): Install GitHits from the Cursor marketplace. - [Vercel connector](https://vercel.com/connect/githits): Connect GitHits through Vercel. - [Manus connector](https://manus.im/app#connectors/all/connector_8387945e-9687-4a71-86b4-8a220dbd5b6b): Connect GitHits to Manus. ## Connect through MCP - [Remote MCP server](https://mcp.githits.com): Connect over Streamable HTTP to use GitHits tools from an MCP client. ## Scan your dependencies [githits-scan](https://github.com/githits-com/githits-scan) finds lockfiles and manifests in your repository and sends the selected package files to GitHits to analyze dependencies and write reports on your machine. - **Generate an SBOM:** Run `githits-scan sbom generate` to produce CycloneDX JSON, SPDX tag-value, or a text inventory of your software components. - **Audit dependencies:** Run `githits-scan audit` to find known vulnerabilities, deprecated releases, outdated or duplicate versions, and mismatches between manifests and lockfiles. - **Report licenses:** Run `githits-scan license report` to list dependency licenses and identify missing license information. - **Check your license policy:** Run `githits-scan license check` to evaluate dependencies against the licenses your team allows. - [Introducing githits-scan](https://githits.com/blog/introducing-githits-scan.md): Generate SBOMs, audit dependencies, and report or check licenses from your repository's package files. - [Scan documentation](https://docs.githits.com/scan/overview): Install Scan, select package files, configure license policies, and run checks in your workflow. ## See GitHits at work - [Code discovery: how agents find and understand dependency code](https://githits.com/blog/code-discovery-not-code-search.md): Follow an httpx 0.28.1 investigation from a timeout definition to research identifying the replacement for an unsupported proxy option. Shows direct source lookup and delegated research through CLI, MCP, and API. - [Does your model know the library version you're using?](https://githits.com/blog/model-knowledge-map-githits-api.md): Providing version-specific API definitions through GitHits raised correct API calls from 59.9% to 93.7% across five models on 173 new coding tasks. - [Scaling cloud agents without losing track of their dependencies](https://githits.com/blog/sandbox-footprint-clone-vs-githits-api.md): DeepSeek V4.1 Flash agents read every dependency at the pinned version in all 192 GitHits runs, versus 94.8% with agent-managed clones. Shows a factory workflow where each sandbox clones its job repository and reads external dependencies through the API. - [Finding where a library error comes from with the GitHits API](https://githits.com/blog/error-root-cause-agent-githits-api.md): An agent searches the specified library version and reads matching source to locate the file and function behind an error. Tested on 110 errors across Python, npm, Go, and Rust. - [Checking dependency upgrades for changed defaults](https://githits.com/blog/reviewing-dependency-bumps-githits-api.md): Six models review 81 Python upgrade PRs by checking which application calls rely on defaults that changed. Compares model memory, installed source, and access to both releases through GitHits. ## Explore the index As of November 9, 2026, the GitHits index covers 50,680 open-source repositories (51.21 billion lines of code, 1.22 billion functions across 31 languages), 2.01 million documentation pages from 5,245 sites, and tracks 40,016 packages across 13 registries, with 291,185 security advisories mapped to affected packages. Updated Nov 9, 2026, 9:15 AM UTC - [Index explorer](https://index.githits.dev/): Browse indexed packages, repositories, documentation, and their available versions. - [The Index](https://githits.com/the-index.md): Coverage statistics, metric definitions, and indexing activity. Supported public targets can be indexed on demand. - [Public index stats feed](https://assets.githits.com/indexing/v1/status.json): Read the latest totals and their `generatedAt` timestamp. ## When to use GitHits - Use GitHits to discover, understand, evaluate, and work with public open-source projects throughout development. - For a known package, repository, or documentation site, search and read that target. Use example discovery for broader questions across projects and research for a delegated investigation. - Specify a package version or repository revision to investigate a particular release. ## When not to use GitHits - Use workspace tools for local files, private repositories, and uncommitted changes. GitHits indexes public open-source material. ## Authentication - [Web app](https://app.githits.com): Sign in and manage your GitHits account. - 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 on skills.sh](https://skills.sh/githits-com/githits-cli): Install the GitHits agent skills with `npx skills add githits-com/githits-cli`. - [GitHits MCP](https://github.com/githits-com/githits-cli/tree/main/skills/githits-mcp): Choose the appropriate tools to investigate public code, documentation, and packages. - [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): Integration guidance, API access, and current contract status for factory builders. - [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): How dependency behavior, version mismatches, and repeated source investigation affect an agent's work. - [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 source inspection, documentation, and package information support dependency decisions throughout development. - [The Builders](https://githits.com/the-builders.md): The team building GitHits and the origin story behind the product. - [Software Factory Directory](https://githits.com/software-factories.md): Curated directory of software factories, AI coding agents and agent orchestration tools, with category pages and one page per product. - [FAQ](https://githits.com/faq.md): Who GitHits is for, how it works alongside your agent, index coverage, data handling, and open-source licenses. - [Support / Contact](https://githits.com/support.md): Documentation and contact options for product, access, and commercial questions. ## 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. Discover, use, debug, and maintain dependencies through one interface for new builds, maintenance, and migrations. - [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 Ask your agent: > Browse GitHits blog posts published since October 2026. Read the ones relevant to our product, stack, and workflows, then explain where GitHits could help us. - [Blog index](https://githits.com/blog.md): Engineering investigations, experiments, and workflows for agents working with open source. - [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. ## 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.
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |