Nestjs Validation Pipes
NestJS validation and pipes best practices. Use when validating or transforming request input in NestJS — DTO validation, ValidationPipe, class-validator/class-transformer, or custom pipes. Triggers on ValidationPipe, @IsString/@IsEmail, ParseIntPipe, whitelist, or transform.
Install
$ agentstack add skill-dkmqflx-nestjs-best-practices-plugin-nestjs-validation-pipes ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-dkmqflx-nestjs-best-practices-plugin-nestjs-validation-pipes) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
NestJS Validation & Pipes
Pipes run before route handlers to validate and transform incoming request data. Combined with class-validator and class-transformer, they keep DTOs the single source of truth for input shape and constraints.
When to Apply
- Validating request bodies, query params, or route params in a NestJS app.
- Configuring
ValidationPipe(globally or per-route). - Annotating DTOs with
class-validatordecorators. - Coercing param types with built-in parse pipes (
ParseIntPipe,ParseUUIDPipe, ...). - Writing a reusable custom pipe via
PipeTransform.
Rules
global-validation-pipe- RegisterValidationPipeonce inmain.tsso every endpoint is validated.whitelist-strip-unknown- Usewhitelist+forbidNonWhitelistedto strip or reject unexpected properties.transform-payloads- Enabletransform: trueto auto-instantiate DTO classes and coerce primitive types.dto-classes-not-interfaces- Define DTOs as classes; interfaces are erased at runtime and carry no metadata.class-validator-decorators- Annotate every DTO field withclass-validatordecorators.nested-object-validation- Use@ValidateNested+@Typeto validate nested DTOs and arrays.built-in-parse-pipes- UseParseIntPipe/ParseUUIDPipe/ParseBoolPipeto coerce and validate params.custom-pipe-implementation- ImplementPipeTransformfor reusable custom validation or transformation.
How to Use
Read the relevant file under rules/ for the topic at hand. Each rule states why it matters and shows an incorrect vs. correct example. Apply them when writing or reviewing NestJS input-handling code.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dkmqflx
- Source: dkmqflx/nestjs-best-practices-plugin
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.