Software factories
Equip your factory's agents to use open source right
GitHits connects your factory's agents to the open-source ecosystem through one interface. Its version-aware index brings code, documentation, and package data together so your agents can build on existing work when creating new apps, maintaining older systems, or planning migrations.
Reusing a library takes more than installing it
Every app brings different requirements. Open-source libraries can supply capabilities it needs, but your agents still have to choose libraries that fit the app, integrate their APIs correctly, and account for their dependencies and version changes.
That knowledge is spread across source code, documentation, and package registries. Model training alone can't give agents a dependable picture of an unfamiliar library, a new release, or an older application's dependencies.
Build on open source with confidence
Equip your agents to discover existing solutions, evaluate components, integrate them, and maintain the applications that depend on them. GitHits supplies the code, documentation, and package details they need to investigate those decisions throughout development.
- Build on existing solutions. Agents can find how other open-source projects solve a problem, then investigate candidate libraries and their integration requirements.
- Check dependencies throughout development. Agents use the same interface to evaluate packages, implement and review integrations, debug failures, and prepare updates.
- Know why a component fits the app. Agents can check its API, license, dependency requirements, and known vulnerabilities before building on it.
Use it when building a new app, maintaining an older system, or migrating to a different library or release. Agents can inspect older installed versions as well as new ones, including those missing from the model's training.
The developer workflow, carried out by agents
Developers have long relied on documentation, source code, and working examples to choose and use libraries. Your factory delegates that work to agents. To assess their decisions, you need to see which APIs, package details, and version constraints they checked against the app's requirements.
For example, when an app needs PDF extraction, your agent can use GitHits to find how other projects parse PDFs, then evaluate a candidate parser's license and dependencies. It reads the chosen version's source and consults documentation and usage examples before wiring the parser into the app's upload flow.
If parsing fails, it can trace the error into the library. When the app needs a newer parser, it can inspect release changes before updating the integration. Your factory's agents use GitHits throughout the work to check how the library fits and behaves in the app they're building.
Build GitHits into your factory
Connect through MCP or the CLI, or embed the REST API in your planning, coding, review, and update steps. Control when agents retrieve information and how it enters their context, within your own product experience.
If your product runs or configures customers' agents, make GitHits available through MCP in their setup.