Nowadays modern software projects are using multiple package managers at the same time. It’s very common to use Bower.io for frontend dependencies and NPM for dependencies on the server side. So it comes that the same Git repository contains a bower.json and a package.json file. Both can be monitored by VersionEye. Up to now if the switch was flipped in our Git interface that created always a sperate project at VersionEye and there was a manual step involved to merge the 2 projects to 1 logical project.
The new behavior is that VersionEye is checking if there is already an existing project for the corresponding user from the same SCM provider, same repository and same branch. If all that is true the new project will be merged automatically into the existing one. The 2 flipped switches from above would result into a project with 1 child project like here:
Of course a subproject can be unmerged again into a separate project. But most of the time this behavior makes sense.
Open Source License Compliance & Security 