security-vite

Audit Vite apps for VITE_* exposure, secret leakage, and proxy misconfigurations.

7|2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/justinlevinedotme/jalco-opencode --skill security-vite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-vite
Source: https://github.com/justinlevinedotme/jalco-opencode/tree/main/opencode/.config/opencode/skills/security-vite
Command: npx skills add https://github.com/justinlevinedotme/jalco-opencode --skill security-vite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Security vulnerabilities in Vite apps arise from misconfigured env vars, exposed build-time secrets, and insecure dev server settings. This Skill provides a structured approach to auditing Vite projects for these issues, enabling proactive hardening.

Core Features & Use Cases

  • Environment variable exposure checks for VITE_ vars.
  • Build config and source maps checks to prevent secret leakage and insecure builds.
  • Dev server host binding and proxy security validations for vite.config.ts setups.
  • SPA authentication and security checks to ensure server-side protection, not only UI guards.

Quick Start

Scan your Vite project with this skill to identify VITE_* exposure, secret leakage, and insecure dev server configs.

Frequently Asked Questions about security-vite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Vite environment variables for secret leakage?

Auditing Vite environment variables requires checking VITE_* prefix exposure, validating env file priority loading, and detecting define blocks leaking build-time secrets into client bundles.

What is a Vite proxy misconfiguration in the dev server?

A Vite proxy misconfiguration occurs when dev server proxy settings and host bindings in vite.config.ts are insecurely set, exposing backend endpoints or allowing unauthorized network access during local development.

How do I secure VITE_ variables in my Vite SPA?

Secure VITE_ variables by enforcing server-side authentication checks rather than relying solely on UI guards, verifying that exposed environment variables do not contain secrets, and validating build config source map settings.

Does this Vite security audit check both dev server and build config settings?

Yes, the Vite security audit checks both dev server settings and build configurations, covering proxy misconfigurations, host binding vulnerabilities, source map secret leakage, and define block exposures across typical vite.config.ts setups.

What files do I need to provide to audit Vite app security?

You need to provide access to your vite.config.* files and environment files, enabling the audit to evaluate environment variable exposure, proxy settings, and security hardening patterns across your Vite setup.