PureScript Registry
registry.purescript.org
- Web
- API
6.2 Club score Visit registry.purescript.org
What the maker publishes
- API operations
- The API supports registering, publishing, updating, transferring, and unpublishing packages, along with package set updates. source
- Build checks
- The specification says registry packages are verified to solve and compile with at least one supported compiler version. source
- 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. source
- Integrations
- Spago integrates with the registry for package publishing and installation, and published documentation is uploaded to Pursuit. source
- Integrity
- The registry records SHA256 hashes for package tarballs so package managers can verify downloaded packages. source
- Integrity
- Published package tarballs have SHA256 hashes that package managers can use to verify integrity. source
- Manifest limits
- To add or update a package, it must contain a bower.json, spago.dhall, or purs.json manifest; legacy manifests are still accepted for now. source
- Owner security
- Sensitive package actions such as transfers and unpublishing require an authenticated operation signed with an SSH key belonging to a package owner or registry trustee. source
- Package age limit
- The specification says packages published before May 2019 are not included if they cannot satisfy the registry's compiler compatibility requirement. source
- Package locations
- Packages can be published from supported locations including arbitrary Git repositories, not only GitHub. source
- Package manager use
- Most PureScript users interact with the registry through package managers; the repository says Spago is the only package manager with official registry support. source
- Package publishing
- The registry fetches package source from a specified location, validates and compiles it, creates a tarball, and updates its indexes. source
- 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. source
- Package sets
- Curated package sets list package versions known to compile together and are updated daily. source
- Package storage
- The registry stores package source tarballs for package managers to download. source
- Publication model
- Authors request that the registry fetch package code from a public location rather than uploading package files directly. source
- Publishing access
- Anyone can publish a package version, while unpublishing or transferring a package requires an authenticated operation by a package owner. source
- Publishing workflow
- The registry fetches package code from a remote location, attempts to compile it, uploads documentation to Pursuit, and adds it to the day's package set batch. source
- Purpose
- The PureScript Registry is a package registry for the PureScript programming language. source
- Purpose
- The PureScript Registry stores PureScript packages and metadata and provides an API for package operations. source
- Pursuit integration
- After a successful package publish, the registry attempts to publish the package documentation to Pursuit. source
- Spago integration
- Spago is identified as the standard PureScript package manager and the registry's reference implementation. source
- Support and administration
- The repository directs authors who want to publish without Spago to open an issue using its Publish workflow. source
- Supported manifests
- The registry currently accepts packages with a purs.json or spago.yaml manifest. source
Checked against the maker's pages on 9 Oct 2026.