JSConf JP

DaloyJS - The first TypeScript REST API framework built for secure AI-assisted services

SessionTrack AEnglish

Every framework's docs page claims "secure defaults." Then you read the source and find body limits set to Infinity, JSON parsers vulnerable to prototype pollution, no request timeouts, and error responses leaking stack traces. Meanwhile, your dependency tree is quietly full of packages with unchecked install scripts, no release-age delay, and lockfiles no one ever verified against source. DaloyJS has an extraordinarily detailed, defense-in-depth security posture covering runtime protections, supply-chain integrity, CI gates, CSRF/CORS/JWT handling, mTLS, IP reputation, SSRF defense, and much more — all as first-party built-ins rather than opt-in plugins.

I'll walk through what actually shipping a secure-by-default HTTP framework looks like in 2026 — at both layers. At the runtime layer: bounded body parsing, prototype-pollution-safe JSON, path-traversal rejection, request timeouts that survive backpressure, Helmet-grade headers, and RFC 9457 problem+json errors, all on by default, all measurable. At the supply-chain layer: blocked lifecycle scripts that can't phone home on pnpm install, a 24-hour release-age cooldown to let fresh-package attacks surface, source-verified lockfiles that catch git deps and non-registry tarballs before CI ships them, and hardened GitHub Actions with pinned steps and no stray credentials.