Unverified50% confidenceFactExact time
A lockfile is a file generated by a package manager after installing dependencies, recording the exact version, download address and integrity checksum of each dependency package.
1
Sources
50%
Confidence
Long-term
Relevance
10/26/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedLockfiles (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.78% similarUnverifiedDependency locking mechanisms (such as Gradle's lockfile and Maven's dependency lock) persist resolution results along with source information into files; after a repository change, checksums or source records may no longer match, and the lock files need to be regenerated.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.73% similarUnverifiedIn CI, --frozen-lockfile can be configured to detect whether the lock file is consistent with package.json, avoiding unexpected drift.69% similarVerifiedA 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.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1098999API
curl https://kongchang.com/api/v1/knowledge/claims/1098999MCP
get_claim(id=1098999)