Featured
Posted by
Crista Perlton on December 11th, 2025.
If you’re managing projects that rely on multiple teams delivering consistent components, you’ve probably noticed the chaos that comes from storing build artifacts and libraries in shared folders. Each team has its own way of organizing files, versions get mixed up, and no one really knows which asset the project should be using....
Featured
Posted byCrista Perlton on December 9th, 2025.
You’re likely pulling OSS packages straight from NuGet.org, npmjs.com, or PyPI.org, via the CLI. It’s the path of least resistance and the fastest way to get what your teams need. But without something sitting in the middle, it’s hard to know exactly what’s being pulled in or whether it meets your org’s requirements. When you pull OSS...
Featured
Posted byCrista Perlton on December 4th, 2025.
Internal registries are a smart way to manage OSS packages. They let you curate reusable code for your apps and cut down on risky repeat pulls from the wild. But when every team spins up its own siloed registry and tooling sprawls across the org, you end up with duplicate work, outdated packages, and security headaches that didn’t need...
Featured
Posted by
The Inedo Team on December 2nd, 2025.
Small delays, hidden dependencies, and tightly coupled systems can turn even minor updates into major headaches. Teams fall short of achieving what was intended as backlogs grow, urgent orders slip, and firefighting becomes the norm. Our latest webinar looks at these challenges through the story of LogistiCorp, a mid-sized...
Featured
Posted byCrista Perlton on November 28th, 2025.
Inedo’s newest whitepaper, “Migrating from Sonatype to ProGet“ releases this month, available both as a free PDF eBook, or as a series of articles on our blog. Migrating from Sonatype Nexus to ProGet is more than just copying your packages over. Nexus spreads its features across different products—Repository, Lifecycle,...
Featured
Posted byCrista Perlton on November 25th, 2025.
Many teams pull open-source packages into their projects without thinking twice. They might stash them locally, pass them around through CI pipelines, or build and test on their own. But without internal repositories or any guardrails in place, each team ends up working in its own bubble. That kind of flexibility can feel great at first,...
Featured
Posted byThe Inedo Team on November 20th, 2025.
In ProGet 2025.14, we introduced two additional compliance rules to help you vet and monitor open-source packages in your organization. These are considered ProGet 2026 preview features, and represent our general roadmap focus for next year’s release: Software Composition Analysis (SCA) and security. In this article, we’ll...
Featured
Posted byCrista Perlton on November 11th, 2025.
Using GitHub Packages for internal package sharing is a common choice for many teams. Since it’s already part of the GitHub ecosystem, teams adopt it naturally, without spending much time looking over other options. Each project manages its own dependencies, and publishing or consuming internal libraries is relatively straightforward. On...
Featured
Posted byThe Inedo Team on November 7th, 2025.
Although ProGet 2025.14 is a maintenance release, it has three major changes to Debian feeds. We would normally wait until ProGet 2026 for this kind of update, but we’re racing against the clock. There are some upcoming changes in Debian 13 (Trixie) that will not be compatible with ProGet. This blog post serves as a combination of...
Crista Perlton on December 11th, 2025.
The Inedo Team