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 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 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 byCrista Perlton on November 4th, 2025.
Many organizations think that letting independent development teams manage their own package workflows is efficient …but in practice, it’s not. Every team tends to develop “its own way” of versioning, approving, and documenting packages. One might use a NuGet Server, while another stores artifacts on a shared drive....
Featured
Posted by
The Inedo Team on October 28th, 2025.
This article is 5/5 in our series on Centrally Managed Package Repositories, also available as a chapter in our free, downloadable eBook Package Management at Scale Level 5 organizations have made a deliberate choice to adopt a more robust, end-to-end approach. They’ve recognized that standard tools like GitHub, GitLab, and CI platforms...
Featured
Posted byThe Inedo Team on October 21st, 2025.
This article is 4/5 in our series on Centrally Managed Package Repositories, also available as a chapter in our free, downloadable eBook Package Management at Scale If an organization reaches this level, it’s never by accident. It’s a result of deliberate investment in automation, strong governance, and repeatable systems. This level...
Featured
Posted byThe Inedo Team on October 14th, 2025.
This article is 3/5 in our series on Centrally Managed Package Repositories, also available as a chapter in our free, downloadable eBook Package Management at Scale An organization at this level demonstrates a degree of technical maturity and team autonomy, with tailored tools and pipelines across projects. But without centralized...
Featured
Posted byThe Inedo Team on October 7th, 2025.
This article is 2/5 in our series on Centrally Managed Package Repositories, also available as a chapter in our free, downloadable eBook Package Management at Scale Due to the various approaches maturing organizations can take, it can be hard to assess yourself as Level 2, but if any of the following apply, you’re likely iterating within...
Crista Perlton on December 11th, 2025.
The Inedo Team