Freedom251 › Artifact repository software
Packistry
What Packistry is
Packistry is a free, open-source, self-hosted Composer repository for distributing PHP packages. It imports packages from GitHub, GitLab, Gitea, and Bitbucket, then uses webhooks to pull new tags and branches. Repositories may be public or private; private access can use user permissions, personal access tokens, or deploy tokens for machines and CI systems. User accounts support roles and repository access. Authentication sources include OAuth 2.0 and OpenID Connect providers such as GitHub, GitLab, Bitbucket, Google, Okta, Keycloak, and Microsoft Entra ID. You can add Packistry to Composer through composer.json or the Composer CLI and install packages through Composer. Docker deployment is documented for local or cloud use. SQLite is the default database, with MySQL guidance also available. Package archives can use container storage or S3-compatible storage such as MinIO. Production guidance strongly recommends HTTPS and trusted-proxy configuration.
Who it suits
Packistry suits private projects, developer teams, and open-source initiatives that need their own Composer repository. It is useful when package access, CI permissions, and source synchronization must be managed.
What it does well
- Free, open-source Composer repository
- Public and private repository support
- Webhooks synchronize connected source repositories
- OAuth 2.0 and OpenID Connect options
- Docker deployment documentation
What to know first
- Self-hosted deployment is required
- Production guidance strongly recommends HTTPS
- Private access requires configured permissions or tokens
Verdict
Packistry gives PHP teams control over Composer package distribution, source synchronization, and private access. Its self-hosted setup offers flexibility but requires deployment, storage, and security configuration.
Facts from Packistry's own pages
- Access control
- User accounts can be assigned roles and repository access, while deploy tokens grant machines access to selected private repositories. · packistryphp.com, 5 Oct 2026
- Archive storage
- The documentation provides a guide for storing package archives in S3-compatible storage, using MinIO and MySQL in its example. · packistryphp.com, 5 Oct 2026
- Automatic updates
- When a package is added from a connected source, Packistry automatically configures webhooks to update it with the latest tags and branches. · packistryphp.com, 11 Oct 2026
- Composer
- Packistry can be added to Composer configuration as a Composer repository and packages can be installed with Composer. · packistryphp.com, 5 Oct 2026
- Composer setup
- Repositories are added to Composer configuration through composer.json or the Composer CLI. · packistryphp.com, 11 Oct 2026
- Database
- The default installation uses SQLite, and the documentation also provides a MySQL setup guide. · packistryphp.com, 5 Oct 2026
- Data storage
- The default setup stores data and package archive ZIP files under /data in the container; the guides also describe MySQL and S3-compatible storage configurations. · packistryphp.com, 11 Oct 2026
- Deployment
- Packistry can run locally or on a cloud platform using Docker or Docker Compose. · packistryphp.com, 11 Oct 2026
- Deployment option
- The Kamal deployment guide describes obtaining a free TLS certificate through Let's Encrypt. · packistryphp.com, 11 Oct 2026
- Intended users
- The introduction describes Packistry for private projects, developer teams, and open-source initiatives. · packistryphp.com, 5 Oct 2026
- Machine access
- Deploy tokens can grant CI systems and other machines access to assigned repositories. · packistryphp.com, 11 Oct 2026
- Package sources
- Packistry supports importing packages from GitHub, GitLab, Gitea, and Bitbucket. · packistryphp.com, 5 Oct 2026
- Private repositories
- It supports hosting sensitive or proprietary packages in private repositories. · packistryphp.com, 11 Oct 2026
- Product
- Packistry is an open-source, self-hosted Composer repository for PHP packages. · packistryphp.com, 11 Oct 2026
- Repositories
- Repositories can be public or private; private repositories require deploy tokens or specific user permissions. · packistryphp.com, 5 Oct 2026
- Security
- The installation guide strongly recommends HTTPS for production environments. · packistryphp.com, 5 Oct 2026
- Setup requirement
- The Kamal guide lists root server access, an SSH key, a DNS A record, and container registry credentials as prerequisites. · packistryphp.com, 11 Oct 2026
- Single sign-on
- Authentication sources support OAuth 2.0 and OpenID Connect, including GitHub, GitLab, Bitbucket, Google, Okta, Keycloak, and Microsoft Entra ID. · packistryphp.com, 5 Oct 2026
- Source integrations
- It can manage and synchronize Composer packages from GitHub, GitLab, Gitea, and Bitbucket. · packistryphp.com, 11 Oct 2026
- Synchronization
- Packistry uses webhooks to pull the latest changes from source repositories. · packistryphp.com, 5 Oct 2026
- Transport security
- The installation guide recommends HTTPS for production and documents configuring trusted proxies behind a reverse proxy. · packistryphp.com, 11 Oct 2026
- User access
- It supports user accounts and personal access tokens for controlling access to private repositories. · packistryphp.com, 11 Oct 2026
Where Packistry stands on Freedom251
- Artifact repository software#61 of 64