Featured
Posted by
Crista Perlton on March 21st, 2025.
Managing your project’s npm packages starts out simple. But as it grows, not only do the number of packages grow, but so do their dependencies; each with different licenses that may or may not align with your organization’s policies. Assessing them is tedious and time-consuming, and without clear oversight, it’s easy for things to...
Featured
Posted by
Crista Perlton on March 18th, 2025.
Your PowerShell modules are an integral part of your development process. Learn how to care for, create, and get the most out of your PowerShell modules.
Featured
Posted by
Crista Perlton on March 13th, 2025.
An npm package versioned 1.4.5 doesn’t tell you much – certainly not whether it’s stable or what it’s supposed to do. Without context, it’s all too easy to misinterpret the purpose of a build, and this confusion leads to dependency issues, broken builds, or even runtime errors. Worst-case scenario? Unstable...
Featured
Posted by
Crista Perlton on March 7th, 2025.
You’ve seen vulnerability assessments pop up while managing npm packages in ProGet. Running npm audit sparks questions about what vague warnings like “high-severity” warnings actually mean for your applications, leaving you stuck making calls with little context. On top of that, floods of security notifications and...
Featured
Posted by
Crista Perlton on March 6th, 2025.
Using custom tags like beta to call npm packages is a shot in the dark—what do these names even tell you? They’re vague and could point to unstable or entirely different packages. These packages can easily slip into your CI/CD pipeline, installed by an unassuming developer, breaking your production builds. Custom tags lack consistency....