How does Private Packagist handle private code from various version control systems?
Private Packagist can access private code from any Git, Mercurial, or Subversion repository using SSH or HTTP Basic authentication. It supports platforms like GitHub, GitHub Enterprise, GitLab.com, self-hosted GitLab, Bitbucket.org/Cloud, and Bitbucket Data Center/Server.
What happens if an open-source dependency is deleted or its hosting service is down?
Private Packagist mirrors and stores copies of all third-party dependencies. If an open-source dependency is deleted or its original hosting service becomes unavailable, Composer can still install the package from the Private Packagist mirror, ensuring deployment reliability.
How does Private Packagist help with security monitoring?
The platform monitors for security vulnerabilities in both third-party and open-source dependencies. It sends alerts via email, Slack, Microsoft Teams, or webhooks when a vulnerability is reported, and can provide weekly or monthly summaries.
Can Private Packagist manage multiple Composer packages within a single VCS repository?
Yes, Private Packagist supports multiple packages per VCS repository. Users can specify the paths to composer.json files directly or use glob patterns to define multiple locations within the repository.
How does Private Packagist ensure that new package versions are available immediately?
Webhooks notify Private Packagist when changes are made to packages. This allows the platform to update composer.json metadata instantly, enabling immediate composer update execution without waiting for cron jobs or Git clones.
What is the relationship between Private Packagist and the Composer open-source project?
Private Packagist was founded by the creators of Composer and Packagist.org. Subscriptions to Private Packagist directly fund the ongoing development of the Composer open-source project.