PureScript Registry

Web · API

Visit site Alternatives

Freedom report

No signalScore 4.9

Free tierNo free tier on record
Open codeNo open-source code on record
Runs widely1 of 6 device platforms
DocumentedThinly documented

PureScript Registry is ranked #27 of 28 in code transpilers on Freedom251. It runs on API, Web.

Compared on code transpilers

Package ecosystems: single

Best PureScript Registry alternatives

See all 12

Two bars SWC Free tier No. 1Free6.7 Two bars Transcrypt Free tier No. 2Free6.7 Two bars Babel Free tier No. 3Free6.6 Two bars ClojureScript Free tier No. 4Free6.6 Two bars Google Web Toolkit Free tier No. 5Free6.6 Two bars Kotlin/JS Free tier No. 6Free6.6

The record

Purpose: The PureScript Registry is a package registry for the PureScript programming language.
Package publishing: The registry fetches package source from a specified location, validates and compiles it, creates a tarball, and updates its indexes.
Supported manifests: The registry currently accepts packages with a purs.json or spago.yaml manifest.
Package locations: Packages can be published from supported locations including arbitrary Git repositories, not only GitHub.
Package sets: The registry curates package sets of packages known to compile together and attempts to produce new sets daily when eligible packages are available.
Spago integration: Spago is identified as the standard PureScript package manager and the registry's reference implementation.
Pursuit integration: After a successful package publish, the registry attempts to publish the package documentation to Pursuit.
Integrity: The registry records SHA256 hashes for package tarballs so package managers can verify downloaded packages.
Publishing access: Anyone can publish a package version, while unpublishing or transferring a package requires an authenticated operation by a package owner.
Unpublishing limit: A package version can generally be unpublished only within 48 hours of publication, unless the registry must remove it for legal reasons.
Validation limit: A package must contain a src directory with at least one .purs file and compile successfully to pass source verification.
Documentation limit: Publishing documentation to Pursuit requires compiler version 0.14.7 or later, and a documentation publishing failure does not fail the package publish operation.

Where it ranks on Freedom251

Best Code Transpilers in 2026#27 of 28
Best Package Registries in 2026#25 of 28

Is PureScript Registry yours?

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.

Claim it free Promote PureScript Registry

Sources

github.com/purescript/registry-dev/blob/master/SPE· checked 4 Oct 2026