Packistry review
A focused self-hosted repository for teams distributing PHP packages through Composer.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Packistry is an open-source, self-hosted Composer repository for distributing PHP packages. It supports both public and private repositories, giving PHP teams a focused place to manage packages used in Composer projects. Its scope is deliberately narrow: Packistry is built around Composer configuration and package installation rather than a broad set of artifact formats. That makes it a suitable fit for organizations that want control over PHP package distribution and are prepared to operate the repository themselves.
For package flow, Packistry connects with GitHub, GitLab, Gitea, and Bitbucket. Packages can be imported from those services, while webhook-based synchronization helps keep repository contents updated. This gives teams a direct path from source hosting to Composer distribution without changing the repository’s PHP-focused purpose. Docker-based deployment supports self-hosted operation, and the listed web platform provides the management interface. Teams looking for a Composer repository that fits into an existing Git-hosting workflow should find this combination relevant.
Access control is another central part of the product. Packistry provides user roles and repository-level access assignments, along with personal access tokens and deploy tokens for user and machine access. Authentication sources support OAuth 2.0 and OpenID Connect, including GitHub, GitLab, Bitbucket, Google, Okta, Keycloak, and Microsoft Entra ID. Choose Packistry when self-hosting, Composer support, and repository-level controls are priorities. An alternative is a better fit for teams that need multiple artifact ecosystems, a hosted service, or platform coverage beyond the web.
Packistry pros and cons
- Where it wins
- Public and private Composer repositories with package installation support
- Imports and synchronizes packages from four Git hosting platforms
- Role-based access, tokens, OAuth 2.0, and OpenID Connect support
- Where it doesn't
- Focused on Composer packages rather than broader artifact formats
- Self-hosted deployment requires Docker-based infrastructure
- Web is the listed platform, with no broader client coverage
Packistry fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. How we rank.
Last updated · How we research and update