Developer ecosystems · .NET package registry and event catalog
Track .NET package launches, version churn, dependencies, tags, and download-based adoption signals for SDKs, data connectors, and developer tools. Strong fit for founders selling into Microsoft/.NET teams, enterprise APIs, data platforms, and internal developer portals.
Put it to work
Track .NET package launches, version churn, dependencies, tags, and download-based adoption signals for SDKs, data connectors, and developer tools. Strong fit for founders selling into Microsoft/.NET teams, enterprise APIs, data platforms, and internal developer portals.
Use the available ecosystem signals to shortlist a language, platform or integration for further research. Validate adoption signals with conversations about the problem your product solves.
What it covers
Geography: Use the geography stated by the source; coverage can vary by dataset and release.
Granularity: Track .NET package launches, version churn, dependencies, tags, and download-based adoption signals for SDKs, data connectors, and developer tools.
Source type: .NET package registry and event catalog
Access and cost
Documented HTTP endpoints with anonymous examples; package metadata and catalog are available through the service index. Package redistribution and licensing remain governed by individual package terms.
Cost: Current price was not established in this review; check the provider's access terms.
Update cadence: Release cadence was not normalized in this review; check the source's dates, update notes, and API limits before comparing periods.
Before you use it
Download counts are registry metrics rather than unique users; the catalog is time-indexed, and Microsoft notes it is not currently available in China.