Skip to main content

Package Ingestion

Ground can index packages from npm and PyPI registries, providing accurate documentation context for your dependencies.

Why Index Packages?

When AI assistants answer questions about libraries, they often:
  • Use outdated patterns from training data
  • Hallucinate function signatures
  • Provide incorrect usage examples
Ground solves this by indexing the actual package metadata including:
  • README documentation
  • Package description and keywords
  • Type definitions (when available)
  • Version-specific information

Supported Registries

Creating a Package Source

Using SDKs

What Gets Indexed

npm Packages

PyPI Packages

Version Pinning

You can index specific versions:

Search Examples

After indexing packages, search returns accurate context:
Response includes:
  • README sections about debounce
  • Package description
  • Keywords and related utilities

Best Practices

Focus on packages your team actually uses. Don’t index everything from npm.
For production, pin to specific versions to avoid staleness issues.
Index both your code AND your dependencies for complete context.
Set up scheduled syncs to keep package docs fresh.

Limitations

Package ingestion currently focuses on documentation and metadata. Full source code indexing is not yet supported.
  • Source code files are not indexed (only documentation)
  • Private registries not yet supported
  • Scoped packages (@org/package) require URL encoding