Vite Plugin Development

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-only Vite plugin development skill with one copy-paste safety caveat around exposing configuration to browser code.

Safe to install for Vite plugin development. When using the examples, only expose public build metadata or deliberately public app configuration, and never inject tokens, secrets, credentials, private environment variables, or internal settings into frontend bundles.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
89% confidence
Finding
This markdown file contains a code example that injects a user-supplied config object directly into client-side code via Vite's `define` option. Because the section is presented as a pattern for exposing env/config to the client, it lacks any warning that sensitive configuration or secrets must not be included, which is a user-facing disclosure omission under the markdown-file criteria.

VirusTotal

67/67 vendors flagged this skill as clean.

View on VirusTotal