Explore Live Data Guide

Open Source Package Registry Inspector Guide

Inspect release versions, dependencies, license compliance, and sizes across npm, PyPI, and Crates.io.

Overview

Inspect software package health and metadata across npm (JavaScript), PyPI (Python), and Crates.io (Rust). Verify latest releases, declared licenses, dependency counts, author contacts, and repository links.

When to Use Open Source Package Registry Inspector

Use Open Source Package Registry Inspector when evaluating third-party dependencies, conducting license compliance audits, or checking release versions.

Inputs, Formats & Specifications

Accepted Inputs
Ecosystem selector (npm, PyPI, Crates.io), Package Name string
Output Formats
Latest version, description, declared license, repository URL, maintainers, direct dependencies, publication date
Supported Standards
npm Registry JSON, PyPI JSON API, Crates.io API v1
Browser Limits & Scope
Inspects public, published open-source packages; private corporate registries (private npm/Artifactory) are not queried.

How to use Open Source Package Registry Inspector

  1. Select your target software ecosystem: npm (JavaScript), PyPI (Python), or Crates.io (Rust).
  2. Enter the package name (e.g. `express`, `requests`, or `serde`) into the search field.
  3. Click 'Inspect Package' to query official public registry APIs directly from your browser.
  4. Review the package summary card showing latest version, declared license, author contacts, and repository links.

Real-World Examples

npm License Compliance AuditCheck the declared license (e.g. MIT vs AGPL) and direct dependency count of an npm utility before adding it to an enterprise application.
PyPI Package Release CheckVerify the latest published version and author homepage link for a Python library before upgrading requirements.txt.

Frequently Asked Questions

Which package registries are supported?

This inspector queries npm (JavaScript/TypeScript), PyPI (Python Package Index), and Crates.io (Rust) via their official public APIs.

Does this require an npm or GitHub token?

No. All queries inspect public, unauthenticated registry metadata using direct HTTPS requests.

How does it detect license compliance?

It reads the standardized `license` field in the package manifest (e.g. SPDX license identifiers like MIT, Apache-2.0, BSD-3-Clause).

Privacy & Data Security

Open Source Package Registry Inspector queries verified public open data directly from your browser with zero tracking and zero API keys.

Last updated:

Related Tools