Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent Go/Vercel API helper skill; it uses a Vercel token for expected authentication and discloses the main safety limits.
Before installing, review the third-party Go module and use a least-privilege Vercel token stored securely, preferably in an environment variable or secret manager. Be careful with methods that can change or delete Vercel projects, deployments, domains, DNS records, environment variables, or teams, and only run them for resources you intend to manage.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Go 1.26.9 or newer, per the module's `go.mod`.
- Runtime dependency: `github.com/oapi-codegen/runtime`.
- A Vercel access token, created under Account Settings, Tokens.
## Install
This markdown file tells users to create a Vercel access token and later use it in an Authorization header, but it does not warn that the token is sensitive or should be stored securely. For markdown files, credential- or privacy-affecting behavior should be accompanied by a user-facing warning when omitted.
The file explicitly instructs users to set an Authorization bearer token on every request, which affects privacy and credential handling. The description does not warn users to avoid logging the header, exposing it in code samples, or otherwise mishandling sensitive request data.
No suspicious patterns detected.