Vendayx
Vendayx is a lightweight VS Code extension that scans supported source and configuration files for likely hardcoded credentials. Scanning is local and offline: source text and credential values are not uploaded or written to logs or findings. Vendayx is a best-effort detector, not a guarantee that a codebase is secure.
Features
- Scans Java, Python, JavaScript, TypeScript, JSON, YAML, Properties, and environment files when opened, edited, or explicitly requested.
- Reports AWS access key IDs, PEM private-key headers, database URL credentials, and likely password, API key, JWT secret, and authentication-token assignments.
- Highlights findings with VS Code diagnostics and severity.
- Shows counts and clickable, line-linked findings in the Security Dashboard activity-bar view.
- Offers a quick fix that explains moving credentials to environment variables; it does not edit source code.
- Skips common build/dependency directories and files larger than 1 MiB during workspace scans.
- Stores finding metadata only in extension memory. Sensitive values are neither included in messages nor retained.
Install and run locally
- Install Node.js and a current stable version of VS Code.
- In the extension project directory, run
npm install.
- Open this directory in VS Code and press F5 to launch the Extension Development Host.
- In the Extension Development Host, open a project and use the Vendayx icon in the Activity Bar, or run a command from the Command Palette.
To package the extension for local installation, install @vscode/vsce and run vsce package; then install the generated .vsix using Extensions: Install from VSIX.... The project does not require vsce to compile or run tests.
Commands
- Vendayx: Scan Current File
- Vendayx: Scan Entire Workspace
- Vendayx: Clear Results
- Vendayx: Open Security Dashboard
Supported files are scanned automatically when opened and after edits. Edit-triggered scans are briefly debounced.
Custom rules
Add rules in VS Code settings under secretGuard.customPatterns. Each rule requires a unique ID, title, JavaScript regex source, severity (Critical, High, Medium, or Low), description, and remediation. The regex must have a capturing group for the sensitive value; only that capture is highlighted. Custom rules are validated and invalid entries are ignored. Keep expressions specific and efficient: regular expressions are evaluated locally against source lines.
Example settings.json entry:
{
"secretGuard.customPatterns": [
{
"id": "TEAM001",
"title": "Internal service credential",
"regex": "service_secret\\s*[:=]\\s*[\"']?([A-Za-z0-9_-]{20,})",
"severity": "High",
"description": "An internal service credential may be hardcoded.",
"remediation": "Move the value to the team's approved secret store."
}
]
}
Development
npm run compile compiles the extension and tests with TypeScript.
npm test compiles the project and runs the scanner unit tests.
npm run watch watches TypeScript files during development.
Patterns use conservative names and value-length checks to limit false positives. They cannot identify every credential or determine whether a detected value is active. Review findings, rotate any exposed credentials, and use your organization's secret-management practices.