Deno
Secure JavaScript and TypeScript runtime with first-class TypeScript, npm compatibility, and edge deployment.
About
Deno is a secure runtime for JavaScript, TypeScript, and WebAssembly, created by Node.js co-creator Ryan Dahl and written in Rust on V8. Its defining trait is secure-by-default: scripts get no file, network, or environment access unless explicitly granted. Deno 2 closed the ecosystem gap with full npm and Node.js compatibility, so existing packages run unmodified, while TypeScript works out of the box with no build step.
The MIT-licensed project has 108,000+ GitHub stars and commercial backing through Deno Deploy (edge hosting), Deno KV (key-value storage), and the JSR package registry. For AI agents and tooling, the permission model is the draw: run untrusted generated code with a tight sandbox instead of a full container.
What it can do
- Secure-by-default runtime with explicit permissions
- First-class TypeScript with no build step
- Full npm and Node.js compatibility (Deno 2)
- Built-in test runner, formatter, and linter
- Deno Deploy, Deno KV, and the JSR registry
Setup
Install with the official install script, then run scripts with explicit permissions, for example deno run --allow-net app.ts.
Prerequisites
None beyond the installer; familiarity with JavaScript or TypeScript.
Use cases
Works with
Trust score — 9/10
Scored 9/10 (verified tier, metrics-v1). Evidence: 108,692 GitHub stars; MIT license confirmed via GitHub API; Deno 2 npm/Node compatibility, permission model, and TypeScript-first design verified against official docs; Commercial backing via Deno Deploy, Deno KV, and JSR registry. Manual review: claims about secure-by-default sandboxing verified from docs; founder fact (Ryan Dahl) is public record. License: MIT.
★ 108,692 GitHub stars
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.