Know what the application includes

List direct and indirect packages, runtime libraries, plugins, build tools and container base images. Record the version, source, owner and application that uses each component.

A dependency can introduce risk even when your code does not call it directly. Build systems and release tools also need an owner and a supported update path.

Set a review and update process

Use trusted package sources and lock files where your package manager supports them. Review advisories for the versions you use. Test an update before production when it can change application behaviour.

Prioritise components that are exposed to untrusted input or have access to sensitive data. Remove packages that the application no longer needs.

Verify the released application

Confirm that the production build contains the intended dependency versions. Keep release records and a rollback path. Investigate unexpected package changes before they reach users.

Add dependency checks to the normal development process. A software supply chain review should include repositories, build credentials and release access, not only a package list.