Vercel moved to kill static credentials. Then developers spotted its own deployment token.
Vercel is pushing the ecosystem to eliminate persistent API keys in favor of OpenID Connect (OIDC) and short-lived identity-based tokens, with a January 2027 deadline for Marketplace vendors or risk delisting. The push follows multiple supply chain attacks leveraging stolen credentials, including recent npm worms. However, developers have pointed out that Vercel's own GitHub Actions deployment workflow still relies on the static credentials the company now discourages, creating a credibility gap.
Key points
- Vercel mandates shift from static API keys to OIDC by Jan 2027 for vendors
- Only 8.4% of 1,000+ surveyed SaaS vendors currently support secure auth methods
- Vercel's own deployment uses static credentials, contradicting its own policy
Summary and key points written by AI from the headline and a short excerpt, so they can be incomplete or wrong. The New Stack did the reporting; read the original for the full story.
Read the full story at The New Stack