Automic VaultAutomic Vault

brew

kraken2 mit Homebrew, apt, apk installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install kraken2

local Homebrew formula metadata

Linux

Debian aptverifiziert · 92%
sudo apt install kraken2

Debian stable package indexes · kraken2 · Quelle: deb.debian.org

Alpine Linux apkverifiziert · 92%
sudo apk add k2

Alpine Linux edge package indexes · k2 · Quelle: dl-cdn.alpinelinux.org

Überblick

Paketzusammenfassung

Taxonomic sequence classification system

Befehle und Aliase

  • k2
  • kraken2
  • kraken2-build
  • kraken2-inspect

Verlauf

Projektgeschichte und Nutzung

Kraken 2 is the second-generation Kraken taxonomic sequence classifier for DNA reads. It matters in bioinformatics packaging because it packages a high-performance, database-heavy scientific CLI into standard Unix package-manager workflows while still reflecting the research tool's unusually large external data requirements.

Projektgeschichte

The original Kraken classifier was published in Genome Biology in 2014 as an ultrafast metagenomic sequence classification method based on exact k-mer alignments. Kraken 2 was created after Kraken 1's speed exposed a practical problem: large k-mer/LCA databases could demand enough RAM to make the tool hard to run on ordinary workstations.

Kraken 2's manual describes the key redesign: it stores minimizers instead of every k-mer, uses a probabilistic compact hash table, supports translated search against amino-acid databases, and adds spaced seeds and special database support. The Kraken 2 paper was published in Genome Biology on 2019-11-28 and reported lower memory use and faster classification while keeping Kraken-style exact-match taxonomy assignment.

Adoptionsgeschichte

Kraken 2 became part of the common metagenomics command-line toolkit because it preserved Kraken's CLI-centered workflow while reducing the memory barrier for large microbial reference databases. Its Homebrew, Debian, Ubuntu, Alpine, and source-build packaging reflects the way sequencing labs and HPC users install reproducible command-line tools across mixed Linux and macOS environments.

The project also kept compatibility with the surrounding Kraken ecosystem, including the original Kraken paper lineage and related abundance-estimation workflows such as Bracken, which helped make Kraken 2 an upgrade path rather than a disconnected replacement.

Wie es verwendet wird

Users install the program, then build or download a taxonomy database before classifying reads with commands such as kraken2, kraken2-build, and kraken2-inspect. The manual emphasizes that database construction depends on external taxonomy and sequence downloads, disk space, RAM, OpenMP-capable builds, and Unix utilities.

For package managers, Kraken 2 is an example where the packaged executable is only part of the operational story: the large mutable reference database, network downloads, and local storage policy matter as much as the binary.

Warum Paket-Nerds sich dafür interessieren

Kraken 2 is a package-nerd case study in scientific software distribution: a small CLI package fronts a large and evolving data dependency that cannot simply be vendored into the formula. It also shows why bioinformatics packages often need both upstream manuals and package-manager metadata to communicate runtime expectations.

Zeitleiste

  • 2014: The original Kraken paper was published in Genome Biology.
  • 2018-06-26: The Kraken 2 GitHub repository and v2.0.6-beta release were published.
  • 2019-11-28: The Kraken 2 paper was published in Genome Biology.
  • 2025-11-24: Kraken 2 v2.17.1 was published on GitHub.

Related projects

  • Kraken 1 is the direct predecessor. Bracken is a related abundance-estimation tool commonly used with Kraken classification output. The broader method family includes other metagenomic classifiers and low-memory variants that respond to the same taxonomy-indexing tradeoffs.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 4 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
k2cliglobales Executable
kraken2cliglobales Executable
kraken2-buildcliglobales Executable
kraken2-inspectcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-10
Manager-Version2.17.1
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.17.1

https://github.com/DerrickWood/kraken2

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:kraken2
Version2.17.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/kraken2
Homepagehttps://github.com/DerrickWood/kraken2
Repositoryhttps://github.com/DerrickWood/kraken2
Upstream-Dokumentationhttps://github.com/DerrickWood/kraken2/blob/master/docs/MANUAL.markdown
LizenzMIT
Quellarchivhttps://github.com/DerrickWood/kraken2/archive/refs/tags/v2.17.1.tar.gz
Abhängigkeitengperftools, libomp, python@3.14, wget
Von macOS bereitgestellte Bibliothekenperl, rsync
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namekraken2
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

kraken2 2.1.3-1

taxonomic classification system using exact k-mer matches

https://www.ccb.jhu.edu/software/kraken2/

sudo apt install kraken2
  • Section: science
  • Architecture: amd64
  • 7 Abhängigkeiten
  • normalized package name match
  • Abgeglichen nach: Kraken2
Debian stable package indexes · deb.debian.org · Debian stable package indexes: kraken2 from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Ubuntu apt95%

kraken2 2.1.3-1

taxonomic classification system using exact k-mer matches

https://www.ccb.jhu.edu/software/kraken2/

sudo apt install kraken2
  • Section: universe/science
  • Architecture: amd64
  • 7 Abhängigkeiten
  • normalized package name match
  • Abgeglichen nach: Kraken2
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: kraken2 from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz
apk92%

k2 0_git20260430-r0

Chess engine with UCI and Xboard interface

https://github.com/serg-meus/k2

sudo apk add k2
  • License: GPL-3.0-or-later
  • Architecture: x86_64
  • Source Package: k2
  • 1 Abhängigkeiten
  • 1 stellt bereit
  • installed executable or alias match
  • Abgeglichen nach: K2
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: k2 from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment