Operations | Monitoring | ITSM | DevOps | Cloud

Open source is the backbone of most software. But should developers trust OSS? npm, PyPI, and Maven don't vet packages before publication, so "publicly available" doesn't automatically mean "safe to pull right now." A secure OSS posture is to trust the ecosystem but verify at ingestion: route packages and dependencies through a controlled layer that runs scanning, age checks, and malware detection before anything reaches a build.

Eighty percent of new developers on GitHub start using Copilot within their first week. How many really know what it's pulling in?

Code generation gets all the attention, but one of AI's biggest strengths might be helping non-engineers prototype ideas, explore solutions, and get work done that otherwise never would have happened.

"We'll spend weeks shaving 10 minutes off CI, then let code sit waiting 18 hours for review." Luca and Rob discuss why AI isn't just changing how we write code, it’s forcing teams to rethink the entire software delivery process.

The secure path and the easy path should be the same path. Ralph McTeggart (Principal Engineer), Alex Franzmann (Customer Onboarding Team Lead), and Claire McDyre (Product Manager) at Cloudsmith lay out how platform teams can deliver supply chain security as a capability rather than a checklist. The argument runs from first principles: make a private registry the default, automate policy enforcement at the global level, and extend that same logic to compliance – so SBOM generation happens in the pipeline, not as a developer's manual task.

Stop context-switching between your IDE and CI dashboard. This video shows you how to connect Cursor to CircleCI using the CircleCI MCP server so your AI agent can read pipeline failures, validate configs, and trigger builds without leaving your editor. In this demo, we introduce a bug, let CI catch it, and watch the agent diagnose and fix it autonomously through a full green pipeline. No manual log hunting required.