Unverified50% confidenceFactExact time
Vercel checks supported lockfiles (such as package-lock.json, yarn.lock, pnpm-lock.yaml) before installation, including when dependencies are restored from the build cache.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/2/2026
First Seen
Valid until: 1/31/2027
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.76% 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.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.67% 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.67% similarUnverifiedA 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.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1128004API
curl https://kongchang.com/api/v1/knowledge/claims/1128004MCP
get_claim(id=1128004)