PureScript Registry

Overview

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

Compared on code transpilers

Package ecosystems

singleregistry.purescript.org

Facts

Purpose

The PureScript Registry is a package registry for the PureScript programming language.github.com · 4 Oct 2026

Package publishing

The registry fetches package source from a specified location, validates and compiles it, creates a tarball, and updates its indexes.github.com · 4 Oct 2026

Supported manifests

The registry currently accepts packages with a purs.json or spago.yaml manifest.github.com · 4 Oct 2026

Package locations

Packages can be published from supported locations including arbitrary Git repositories, not only GitHub.github.com · 4 Oct 2026

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.github.com · 4 Oct 2026

Spago integration

Spago is identified as the standard PureScript package manager and the registry's reference implementation.github.com · 4 Oct 2026

Pursuit integration

After a successful package publish, the registry attempts to publish the package documentation to Pursuit.github.com · 4 Oct 2026

Integrity

The registry records SHA256 hashes for package tarballs so package managers can verify downloaded packages.github.com · 4 Oct 2026

Publishing access

Anyone can publish a package version, while unpublishing or transferring a package requires an authenticated operation by a package owner.github.com · 4 Oct 2026

Unpublishing limit

A package version can generally be unpublished only within 48 hours of publication, unless the registry must remove it for legal reasons.github.com · 4 Oct 2026

Validation limit

A package must contain a src directory with at least one .purs file and compile successfully to pass source verification.github.com · 4 Oct 2026

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.github.com · 4 Oct 2026

Where it ranks on Specifiction

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

Sources

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