I'm looking to create a repository in Nexus that only includes specific packages I've chosen from Maven Central. I want to ensure that my team works with a standardized set of packages and versions, filtering out any random choices they might make. I've checked the documentation that mentions Nexus can have proxy or hosted repositories, but I'm unsure how to establish a curated repository. Any advice?
1 Answer
Creating a curated repo is definitely a smart move! Nexus has some features that can help with this. You might want to look into Nexus Firewall and Server IQ, which work together to filter packages based on your set policies. They let you block unwanted downloads or just monitor specific packages based on their licenses and vulnerabilities. It does have a cost per user, though, so keep that in mind when planning. It's also worth checking if there are other tools like Grype that can assist if you're also looking for dependency scanning.
Yeah, but can you really limit it to just the 2000 packages you want the team to use?