Unverified50% confidenceFactExact time
For detected blocked dependencies, Vercel directly fails the deployment and clearly indicates the blocked package name and version in the error message.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/2/2026
First Seen
Valid until: 1/31/2027
Sources
Related Entities
Related Claims
UnverifiedVercel's check is based on a blocklist listing specific package versions flagged for malware or security vulnerabilities.76% similarUnverifiedThe downside of network-layer interception is that it may inadvertently affect other functions and requires ongoing maintenance of a blocklist.64% similarUnverifiedThe limitation of credential masking is that it happens after the fact; if a key has already been written to a remote logging system or leaked through side effects, it is still irrecoverable, and overly aggressive rules may also falsely redact normal output.63% similarUnverifiedVercel checks supported lockfiles (such as package-lock.json, yarn.lock, pnpm-lock.yaml) before installation, including when dependencies are restored from the build cache.61% similarUnverifiedLSCBench's conclusion is that even with security reminders, most tasks remain insecure, with SSRF and information exposure still at the bottom.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1128007API
curl https://kongchang.com/api/v1/knowledge/claims/1128007MCP
get_claim(id=1128007)