
About This Default Registry
Out of the box, the preconfigured Fusion package manager includes multiple default API abstractions for managing packages in a project. GitLab, GitHub, Bitbucket, and the filesystem are intended for local or collaborative development, while this registry serves as the central default for production package releases.
Use this registry to distribute and consume packages across independent projects and prevent identifier conflicts. For custom projects, where you control identifiers, you can stay on your development code platform, such as GitHub or GitLab.
Popular Packages
Explore

Fusion - PHP Package Manager
valvoid/fusion
Reflex - PHP Testing Framework
valvoid/reflex
Parsedown Wrapper
valvoid/parsedown
Maze - PHP Router
valvoid/maze
Mosaic - PHP Template Engine
valvoid/mosaic | announcementRegister Your Package
Group & Package Entries
Create a registry entry for each segment of the package identifier. The final segment is the package entry, while the preceding segments are group entries. Link them in the same order as the identifier to establish the hierarchy.
Valvoid OAuth App
Open your account settings and create a new identity for the source code provider that hosts your package repository. Grant Valvoid permission to read the repository and manage release webhooks.
Synchronize Releases
Assign the provider identity to your package and synchronize it manually to capture existing release tags. Optionally, create a webhook to automatically handle future release events.
Consume Package
Once the event queue has been processed by the 15-minute cron job and the package is synchronized, use Fusion to fetch it. Refer to the documentation for further details.