vue-testing-best-practices
Pass
Audited by Gen Agent Trust Hub on Feb 17, 2026
Risk Level: SAFE
Full Analysis
- Prompt Injection (SAFE): No evidence of instructions attempting to bypass safety filters or override agent behavior. The language is purely instructional and focused on software testing.
- Data Exposure & Exfiltration (SAFE): No hardcoded credentials, API keys, or access to sensitive local file paths (e.g., SSH, AWS config) were found. Network references are limited to reputable documentation sites and standard package registries.
- Obfuscation (SAFE): No Base64, zero-width characters, homoglyphs, or other encoding techniques were used to hide malicious code.
- Unverifiable Dependencies & Remote Code Execution (SAFE): The skill references standard, highly-reputable industry packages (Vitest, Playwright, Vue Test Utils). There are no piped shell commands (e.g., curl|bash) or attempts to download and execute untrusted scripts.
- Privilege Escalation (SAFE): No commands found requiring sudo, administrative privileges, or modifications to system-level configurations.
- Persistence Mechanisms (SAFE): The skill does not attempt to modify shell profiles, startup services, or scheduled tasks.
- Metadata Poisoning (SAFE): Metadata fields are accurate and consistent with the provided content.
- Indirect Prompt Injection (SAFE): While the skill provides templates for processing code, it does not include patterns that would allow external, untrusted data to manipulate the agent's logic.
- Time-Delayed / Conditional Attacks (SAFE): No logic found that triggers specific behaviors based on dates, times, or environment conditions.
- Dynamic Execution (SAFE): No use of eval(), exec(), or runtime code generation from untrusted sources. All code examples are static demonstrations of testing patterns.
Audit Metadata