Results for “namespace-hijacking”

Find dependency confusion risks, where a public package can replace an internal package with the same name. Review dependency files, identify exposed names, and guide registry restrictions and recurring CI checks to prevent substitution.

• Auditing projects that mix private and public package registries
• Checking exposure after internal package names have leaked
• Restricting package sources to approved private registries

Detect and prevent public-over-private name resolution in npm, PyPI, and Maven.

The English summary is being prepared. Showing the original description.