### Problem to solve You can use the GitLab Package Registry to publish and install your Composer dependencies to your Group right alongside your source code and pipelines. The problem is that there are many cases in which you want to publish packages to your project instead of your group. For example, if you have a project that doesn't belong to a group or if you are trying to publish all of your dependencies to one central project to make it easier to download and share dependencies. ### Proposal Create a new project-level endpoint for the GitLab Composer repository that will allow PHP Developers to specify a specific project in their workflows. ### Further details Currently, some of our tests create `projects` without a group, this will then, in turn, fail when a function is trying to use the `group` property of a project This prompted an investigation where it seems not possible to use `parent` or a `project` instead of a `group` to configure a composer package in one's project