opensrc

To fetch dependency source code for offline analysis, request the package source by name. The tool identifies and caches exact package sources from npm, PyPI, crates.io, or VCS references locally to enable deep dives into internal implementations.

Caching dependency source code works by cloning the exact version tag from a registry or VCS reference and storing it locally in the ~/.opensrc/ directory, exposing a path for subsequent offline reads and contextual exploration.

Yes, you can retrieve source code from npm, PyPI, and crates.io. The tool scopes source discovery across these ecosystems and VCS references, enabling exploration of implementation details to improve reasoning about dependency behavior.

The best way to load a full package source tree into an agent context is to ask the tool to fetch the source for a specific dependency. It clones the correct version tag and exposes the local cache path for the agent to read.

You need exact dependency sources to understand how libraries and packages work internally, not just their public APIs. Fetching the full source tree allows agents to explore implementation details, debug a library, or explain its behavior to a teammate.