nestjs-cli
Pass
Audited by Gen Agent Trust Hub on Oct 14, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONEXTERNAL_DOWNLOADS
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill instructions involve interpolating user-provided strings (such as app names, context names, and feature names) directly into shell commands (e.g.,
pnpm dlx @nestjs/cli@latest new <app-name>). This is a standard indirect prompt injection surface where a malicious user could attempt command injection through crafted naming. This risk is inherent to the primary purpose of a CLI-driving skill. - Ingestion points: User-supplied parameters for context, feature, and application names within
SKILL.mdandreferences/new-project.md. - Boundary markers: No specific boundary markers or input validation instructions are provided for these variables.
- Capability inventory: The skill uses
pnpm exec nestandpnpm dlxto execute commands in the shell. - Sanitization: No explicit sanitization or escaping instructions for user input are present.
- [EXTERNAL_DOWNLOADS]: The skill fetches and executes the official NestJS CLI and related schematics using
pnpm. These are well-known packages from a reputable source. - Evidence: Instructions include
pnpm dlx @nestjs/cli@latest new ...andpnpm add -D @nestjs/schematics. - [DATA_EXPOSURE]: The skill mentions the use of
.envfiles for configuration. It correctly advises creating.env.examplefiles and ensuring that local credentials are ignored (e.g., via.gitignore), which aligns with security best practices for credential management. - Evidence:
references/new-project.mdinstructs to create a local.envwith "ignored local credentials" and use it withnest start --env-file .env.
Audit Metadata