Equip your agents to use open source right

GitHits connects coding agents to the open-source supply chain. It gives the agents building and maintaining your applications one interface to public code, documentation, packages, and dependency information through MCP, the CLI, or the API.

A GitHits query identifies a package, repository, version, or ref. For a fixed version, GitHits maps it to a source commit and retrieves the code and documentation attached to that version.

When an agent reaches an unfamiliar API or dependency behavior, it can query GitHits from the coding tool it already uses. It can search for a symbol, read an exact file, inspect release changes, or find prior art in other public projects.

The results include the package version, repository, and source location. The agent can check what the dependency does instead of relying on a remembered API or documentation for another release.

GitHits complements the agent’s access to your local repository. It provides public open-source context without requiring access to your private source.

Find and evaluate dependencies

Your agent needs a way to add file uploads, background jobs, or another capability. Its training may miss a useful library or a recent release. GitHits finds examples grounded in other open-source projects, giving the agent approaches and libraries to investigate.

Once it has a candidate, the agent can inspect package metadata, licenses, known vulnerabilities, and dependencies before choosing what to use.

Use the APIs your version provides

An example that works with one release can fail with another. GitHits lets your agent read the source at the version your application uses and consult the relevant documentation. It can check a function’s parameters, return value, and implementation before writing the integration.

Examples from other projects provide useful starting points. The agent can check their APIs against your dependency version before adapting them.

Debug dependency behavior

When a library throws an unfamiliar error or handles a request unexpectedly, the explanation may be inside the dependency. Your agent can find the error text, locate the responsible function, and read its implementation at the relevant version.

The agent can then trace the behavior back to your integration and decide what to change.

Understand changes before upgrading

A new release can change an API, introduce a dependency, or fix a vulnerability. GitHits gives your agent release notes and an upgrade review covering security, deprecations, and dependency changes.

The agent can then inspect the relevant source versions to understand how the change affects your application and plan the migration.