Verified75% confidenceConceptExact time
A lockfile is a dependency version snapshot file generated by package managers such as npm, pnpm, and yarn, commonly in the form of package-lock.json, pnpm-lock.yaml, or yarn.lock.
3
Sources
75%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiednpm's peerDependencies constraints and lockfiles (package-lock.json, pnpm-lock.yaml) are the first place to look when troubleshooting dependency version mismatches.77% similarVerifiedLockfiles (such as pnpm-lock.yaml, package-lock.json, yarn.lock) record every dependency actually installed by the project and its exact version; when a direct dependency requires a higher version, the package manager will bump the lockfile entry, which may trigger synchronized changes in indirect dependencies.76% similarVerifiedA lockfile (such as package-lock.json or pnpm-lock.yaml) records the exact version and integrity checksum hash of every package in the entire dependency tree, ensuring consistent installation results across different environments.71% similarUnverifiedUsing npm ci or pnpm install --frozen-lockfile in a CI environment installs strictly according to the lockfile and does not resolve semver ranges.70% similarUnverifiedDependency locking mechanisms in software supply chain security (such as npm's package-lock.json and Python's requirements.txt hash locking) alert against silent updates by fixing dependency versions and integrity fingerprints.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1023746API
curl https://kongchang.com/api/v1/knowledge/claims/1023746MCP
get_claim(id=1023746)