Dependency confusion is easy to miss until you look at how your build actually resolves packages.
If your npm or PyPI pipeline can see both private and public registries, make the approved source explicit. Use clear internal names or scopes, keep registry settings in the repo, and pin versions with lockfiles or requirements files.
For UK teams, this is a sensible control to review alongside Cyber Essentials and NCSC guidance. It is practical, low drama, and easier to maintain than relying on local defaults.
Full article: https://clearpathsecurity.co.uk/preventing-dependency-confusion-in-npm-and-pypi-pipelines/?utm_source=tumblr&utm_medium=social