- Home
- Package Registries
- PureScript Registry
On the recordRead 9 Oct 202623 facts
PureScript Registry
On the record
- API operations
- The API supports registering, publishing, updating, transferring, and unpublishing packages, along with package set updates.github.com · read 9 Oct 2026
- Build checks
- The specification says registry packages are verified to solve and compile with at least one supported compiler version.github.com · read 9 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 · read 4 Oct 2026
- Integrations
- Spago integrates with the registry for package publishing and installation, and published documentation is uploaded to Pursuit.github.com · read 9 Oct 2026
- Integrity
- Published package tarballs have SHA256 hashes that package managers can use to verify integrity.github.com · read 9 Oct 2026
- 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.github.com · read 9 Oct 2026
- 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.github.com · read 9 Oct 2026
- Package age limit
- The specification says packages published before May 2019 are not included if they cannot satisfy the registry's compiler compatibility requirement.github.com · read 9 Oct 2026
- Package locations
- Packages can be published from supported locations including arbitrary Git repositories, not only GitHub.github.com · read 4 Oct 2026
- 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.github.com · read 9 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 · read 4 Oct 2026
- Package sets
- Curated package sets list package versions known to compile together and are updated daily.github.com · read 9 Oct 2026
- Package storage
- The registry stores package source tarballs for package managers to download.github.com · read 9 Oct 2026
- Publication model
- Authors request that the registry fetch package code from a public location rather than uploading package files directly.github.com · read 9 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 · read 4 Oct 2026
- 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.github.com · read 9 Oct 2026
- Purpose
- The PureScript Registry stores PureScript packages and metadata and provides an API for package operations.github.com · read 9 Oct 2026
- Pursuit integration
- After a successful package publish, the registry attempts to publish the package documentation to Pursuit.github.com · read 4 Oct 2026
