A validation framework.
Give me a string and I'll tell you if it's a valid npm package name
A module for serving static files. Does etags, caching, etc.
No description provided.
Email address and domain validation
TypeScript definitions for validate-npm-package-name
Street Address Parser for Node.js
Validates whether a string matches the production for an XML name or qualified name
Check if a buffer contains valid UTF-8
Loosely validate an event.
Email address and domain validation
User validations for npm
Function to validate access token received from azure active directory. Useful when you're using a msal library to authenticate users on the frontend and you wanna verify Microsoft tokens in the API.
A better decodeURIComponent
Validate an email address according to RFCs 5321, 5322, and others
JSON Schema definitions for SMPTE ST 2067 IMF types — validates imferno export output
Check if a string is SVG
Offline HTML5 validator and linter
Give me a string and I'll tell you if it's a valid npm package license string
Validate identifier/keywords name
Validate plugin/preset options
I said I want **SIMPLE** runtypes. Just functions that validate and return data. Combine them into complex types and TypeScript knows their structure. That's how runtypes work.
cron-validate is a cron-expression validator written in TypeScript.
Object schema validation
protoc-gen-validate's validation for prost
protoc-gen-validate's validation generation using prost-build
the prost-validate derive
the prost-validate derive implementation
validation types with prost and prost-reflect support
Coming soon…
Typed `Violation` enum + per-Spec `Validate` impls. Every macro Spec gets structural correctness checks BEFORE materialization — empty trait names, unbound splice holes, duplicate bundle members, malformed crate names. Forge refuses to write specs with violations.