deno

A modern runtime for JavaScript and TypeScript.

deno@2.9.6 was published on 2026-08-27. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All deno versions · Permanent reference to 2.9.6

Package specifications

Version2.9.6
License declarationMIT
Published2026-08-27T17:36:36.711Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count6
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size11.13 KiB
Published file count6
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies6
Repository stars108789
Repository forks6466

Install deno 2.9.6

npm install deno@2.9.6
pnpm add deno@2.9.6
yarn add deno@2.9.6

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review3/10 — Found 11/30 approved changesets -- score normalized to 3
Maintained10/10 — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
License10/10 — license file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Packaging10/10 — packaging workflow detected
Binary-Artifacts0/10 — binaries present in source code
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Fuzzing10/10 — project is fuzzed

Evidence and freshness