Where does the downloaded source code go?

All fetched source code is stored in a local directory named `opensrc/` within your current project path.

Does this skill support monorepos?

Yes, it downloads the repository structure so you can navigate subpackages typically found in the `packages/` directory of modern monorepos.

How can I check which packages have already been downloaded?

You can view the `opensrc/sources.json` file to see a list of all currently fetched packages and their metadata.

How do I fetch multiple packages at once with opensrc?

You can download multiple packages in a single command by listing them after the npx call, for example: `npx opensrc package1 package2 package3`.

Is it necessary to delete the source code after use?

It is highly recommended to run `rm -rf opensrc/ ` after your analysis to save disk space and prevent large source files from cluttering your project workspace.

NPM Source Explorer

Name: NPM Source Explorer
Author: andreasasprou

byandreasasprou

•

Developer Tools

Downloads and analyzes npm package source code to understand internal implementations and debug complex library behaviors.

About

The opensrc skill empowers Claude to go beyond documentation and TypeScript definitions by fetching the actual source code of npm packages directly into your environment. This is essential for debugging 'black box' library behavior, understanding internal architecture patterns, or verifying implementation details in monorepos. By integrating with local search and read tools, it allows for a deep-dive analysis of how a library functions under the hood, ensuring more accurate integrations and faster troubleshooting of third-party dependencies.

Key Features

Support for complex monorepo structures (e.g., Vercel AI SDK)
Tracking of downloaded assets via sources.json
8 GitHub stars
Standardized workflow for source exploration and disk cleanup
Instant local fetching of any npm package source code
Deep-code search capabilities using Grep and Read tools

Use Cases

Studying internal patterns of popular libraries to improve your own code architecture
Debugging unexpected library errors when documentation is insufficient
Verifying runtime logic when TypeScript types are missing or inaccurate

About

Key Features

Support for complex monorepo structures (e.g., Vercel AI SDK)
Tracking of downloaded assets via sources.json
8 GitHub stars
Standardized workflow for source exploration and disk cleanup
Instant local fetching of any npm package source code
Deep-code search capabilities using Grep and Read tools

Use Cases

Studying internal patterns of popular libraries to improve your own code architecture
Debugging unexpected library errors when documentation is insufficient
Verifying runtime logic when TypeScript types are missing or inaccurate