# deno mit Homebrew, apk, chocolatey, MacPorts, Nix, pacman, zypper, scoop, winget, apt installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für deno in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:deno
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install deno
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install deno
```

  Evidenz: MacPorts ports tree: devel/deno/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- apk (92%):

```sh
sudo apk add deno
```

  Evidenz: Alpine Linux edge package indexes: deno from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

- Nix (92%):

```sh
nix profile install nixpkgs#deno
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/de/deno/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S deno
```

  Evidenz: Arch Linux sync databases: deno from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

- zypper (92%):

```sh
sudo zypper install deno
```

  Evidenz: openSUSE Tumbleweed package metadata: deno from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

- Debian apt (92%):

```sh
sudo apt install dx
```

  Evidenz: Debian stable package indexes: dx from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

### Windows

- Chocolatey (92%):

```sh
choco install deno
```

  Evidenz: Chocolatey community package catalog: deno from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','deezer'

- Scoop (92%):

```sh
scoop install main/deno
```

  Evidenz: Scoop official bucket manifest trees: bucket/deno.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

- winget (92%):

```sh
winget install --id DenoLand.Deno -e
```

  Evidenz: Windows Package Manager source index: DenoLand.Deno from https://cdn.winget.microsoft.com/cache/source.msix

## Paketfakten

- **Paketschlüssel:** brew:deno
- **Paketmanager:** Homebrew
- **Version:** 2.9.4
- **Quellzusammenfassung:** Secure runtime for JavaScript and TypeScript
- **Homepage:** <https://deno.com/>
- **Repository:** <https://github.com/denoland/deno>
- **Zuletzt aktualisiert:** 2026-07-23T18:45:32Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- deno (Alias)
- dx (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 2.9.4
## Projektgeschichte und Nutzung

Deno is a modern JavaScript, TypeScript, and WebAssembly runtime with secure defaults, built-in tooling, and a single deno executable. It began as a rethink of server-side JavaScript after Node.js and later expanded toward Node and npm compatibility.

### Projektgeschichte

The Deno repository was created in May 2018. The official Deno 1.0 announcement framed the project as a new runtime for JavaScript and TypeScript outside the browser, influenced by lessons from Node.js and designed around browser-compatible APIs, explicit permissions, first-class TypeScript, promises, Rust, and V8.

Deno 1.0 shipped in May 2020 as the stable CLI. The runtime deliberately bundled common developer tooling so users could run, test, format, lint, and document code without assembling a separate Node-style toolchain.

Deno 2, announced in October 2024, marked a shift from rejecting much of the Node ecosystem to supporting Node.js and npm compatibility. The Deno team described that release as combining Deno's original simplicity and security goals with package.json, node_modules, workspaces, npm specifiers, and private npm registries.

### Adoptionsgeschichte

Early Deno adoption centered on developers who wanted browser-like module loading, TypeScript without a separate compiler setup, and a permission model for command-line scripts. Its official docs still present the tool as a secure-by-default runtime with a built-in formatter, linter, test runner, benchmarker, and package workflow.

After Deno 2, adoption broadened toward existing Node projects because Deno could run in repositories with package.json and node_modules while keeping Deno's own tooling and permission model. The release feed shows continued active releases, including Deno 2.9.0 in June 2026.

### Wie es verwendet wird

Deno is used as a CLI runtime for scripts, services, tests, local tools, web servers, and TypeScript projects. The getting-started docs show deno init creating a project with deno.json, main.ts, and tests, then running TypeScript directly without a separate build step.

Package workflows can use URL imports, JSR packages, npm: specifiers, deno.json, or package.json depending on the project. Deno 2 also supports private npm registry configuration through .npmrc, which aligns it with enterprise Node package workflows.

### Warum Paket-Nerds sich dafür interessieren

Deno is package-nerd catnip because it challenges the usual JavaScript runtime/package-manager split. One executable brings together runtime, installer, formatter, linter, test runner, task runner, dependency management, and docs.

Its history also tracks a major ecosystem lesson: clean-slate runtimes are attractive, but compatibility wins adoption. Deno 2's Node and npm support made the package story less ideologically pure and much more operationally useful.

### Zeitleiste

- 2018: The denoland/deno repository is created on GitHub.
- 2020: Deno 1.0 is announced as the first stable CLI release.
- 2024: Deno 2 is announced with Node.js and npm compatibility.
- 2026: Deno 2.9.0 is published on GitHub releases.

### Related projects

- Node.js is the historical reference point and compatibility target for Deno 2.
- V8 and Rust are core implementation technologies discussed in the Deno 1.0 announcement.
- JSR is Deno's TypeScript-first package registry companion.
- Fresh and Deno Deploy are related Deno ecosystem projects from Deno Land.

### Quellen

- <https://github.com/denoland/deno>
- <https://api.github.com/repos/denoland/deno>
- <https://api.github.com/repos/denoland/deno/releases>
- <https://deno.com/blog/v1>
- <https://deno.com/blog/v2.0>
- <https://docs.deno.com/runtime/>


## Sicherheitshinweise

doc example: JavaScript runtime.

- **Geiger-Risiko:** yellow / hoch
- doc example: JavaScript runtime


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: deno.json, deno.jsonc, package.json
## Andere Paketmanager-Einträge

- Nix - deno: normalized package name match | nixpkgs package indexes: pkgs/by-name/de/deno/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- apk - deno - 2.7.4-r2: normalized package name match | Alpine Linux edge package indexes: deno from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | A modern runtime for JavaScript and TypeScript | https://deno.land/
- apk - deno-bash-completion - 2.7.4-r2: normalized package name match | Alpine Linux edge package indexes: deno-bash-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Bash completions for deno | https://deno.land/
- apk - deno-fish-completion - 2.7.4-r2: normalized package name match | Alpine Linux edge package indexes: deno-fish-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Fish completions for deno | https://deno.land/
- apk - deno-zsh-completion - 2.7.4-r2: normalized package name match | Alpine Linux edge package indexes: deno-zsh-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Zsh completions for deno | https://deno.land/
- pacman - deno - 2.9.4-1: normalized package name match | Arch Linux sync databases: deno from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A secure runtime for JavaScript and TypeScript | https://deno.com
- zypper - deno - 2.9.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: deno from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | A secure JavaScript and TypeScript runtime | https://github.com/denoland/deno
- zypper - deno-bash-completion - 2.9.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: deno-bash-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Bash Completion for deno | https://github.com/denoland/deno
- zypper - deno-fish-completion - 2.9.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: deno-fish-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Fish Completion for deno | https://github.com/denoland/deno
- zypper - deno-zsh-completion - 2.9.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: deno-zsh-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Zsh Completion for deno | https://github.com/denoland/deno
- MacPorts - deno: normalized package name match | MacPorts ports tree: devel/deno/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - deno: normalized package name match | Chocolatey community package catalog: deno from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','deezer'
- Scoop - main/deno: normalized package name match | Scoop official bucket manifest trees: bucket/deno.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - DenoLand.Deno: normalized package name match | Windows Package Manager source index: DenoLand.Deno from https://cdn.winget.microsoft.com/cache/source.msix
- Debian apt - dx - 1:4.4.4-18+b1: installed executable or alias match | Debian stable package indexes: dx from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | OpenDX (IBM Visualization Data Explorer) - main package | https://web.archive.org/web/20080812051658/http://www.opendx.org/
- Debian apt - dx-doc - 1:4.4.4-18: installed executable or alias match | Debian stable package indexes: dx-doc from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | OpenDX (IBM Visualization Data Explorer) - documentation | https://web.archive.org/web/20080812051658/http://www.opendx.org/


## Combined YAML source

View the package source record on GitHub. [combined/deno.yml](https://github.com/mxcl/pkgdb/blob/main/combined/deno.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph