Developer ecosystems · Programming-language package registry
Hackage: coverage and access
Track Haskell package coverage, releases, documentation, categories, and dependency signals for language-specific infrastructure or functional-programming developer products. A focused source for founders building tools for Haskell/functional-programming teams, compilers, reliability infrastructure, or typed data services.
What it covers
Geography and granularity
Geography: Use the geography stated by the source; coverage can vary by dataset and release.
Granularity: Track Haskell package coverage, releases, documentation, categories, and dependency signals for language-specific infrastructure or functional-programming developer products.
Source type: Programming-language package registry
Potential use
Track Haskell package coverage, releases, documentation, categories, and dependency signals for language-specific infrastructure or functional-programming developer products. A focused source for founders building tools for Haskell/functional-programming teams, compilers, reliability infrastructure, or typed data services.
Access and cost
Account or registration
Public browsing, search, package downloads, and API resources; publishing is available through the site's account/upload workflow. Package-specific terms apply.
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.
- Provider page ↗
- Documentation and access details ↗Check the provider's current terms and instructions before use
Interpret carefully
Limits that affect the decision
Hackage reflects the Haskell community and package publication, not total usage or commercial adoption; package maintenance and licensing differ across projects.
Release cadence was not normalized in this review; check the source's dates, update notes, and API limits before comparing periods.
This record summarizes source documentation; Jon Bishop did not conduct an independent audit of the underlying dataset.