Lock a resolved dependency graph without confusing it with trust

A manifest can permit a range of package versions while several dependencies impose overlapping constraints. The resolver chooses concrete versions and graph edges according to the ecosystem's rules, registry state, target, and configuration. npm, pip, and Cargo do not share one universal resolution model. Peer dependencies, optional features, environment markers, and platform wheels can change which artifacts are relevant. Record the installer and target context required by your project instead of assuming a top-level version list describes every package that installation will use.

A lockfile captures a selected result and usually additional source or integrity information according to its format. npm package-lock records a dependency tree; Cargo.lock records resolved package choices. Review lock changes as changes to executable inputs, including newly introduced transitive packages and source locations. A frozen installation mode should fail when the manifest and lock cannot satisfy its contract rather than quietly update the lock in deployment. In npm's documented ci workflow, consistency and installation flags matter; copying a lock without the matching relevant configuration is not an adequate release definition.

A recorded artifact hash can detect that retrieved bytes differ from the approved expected bytes, assuming the hash and its trusted recording are sound. It does not tell you whether those expected bytes contain a defect or malicious build script. pip's hash-checking mode requires hashes across the requirements and their dependencies under its documented restrictions; a partial set does not establish a complete integrity boundary. Different acceptable wheels or source archives may require several approved hashes. Name which artifact variants are permitted and why instead of treating one package version string as one universal byte sequence.

Installation can execute code, compile native extensions, or download additional inputs. A source distribution hash pins that source archive, not every compiler, build dependency, or later network fetch it invokes. An AI package may compile a kernel using the host toolkit or fetch a model outside the package resolver. Inventory those steps separately. Registry access controls and encrypted transport help govern where bytes come from, while integrity checks compare those bytes with a trusted expectation. Neither mechanism replaces review of the selected dependency or containment of build-time execution.

A locked download can disappear, become inaccessible, or require a credential that expires. Availability needs an approved retention or mirror strategy and a tested restoration path. Avoid silently substituting another artifact when retrieval fails; a replacement belongs in an explicit update and verification workflow. Record the base image, interpreter, compiler, installer version, and target architecture needed to interpret the lock. When upgrading, inspect the graph delta, run relevant compatibility checks, and regenerate provenance and inventory for the actual resulting artifact rather than reuse yesterday's supporting documents.

The modular lab illustrates only why rotating labels are poor immutable identities. Reset, set both modulus m=4 and step a=1, predict the return to label zero, then Play or Step through four additions. A later state can reuse an earlier label even though its history differs. This is not a dependency resolver or hash function. A real release should retain the concrete package and artifact identities needed for its target, rather than rely on a mutable tag or a human-friendly version alias as if it could never move.