pkg.soopen package index

brew / Rang 6427

trimal mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install trimal

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#trimal

nixpkgs package indexes · pkgs/by-name/tr/trimal/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Automated alignment trimming in large-scale phylogenetic analyses

Befehle und Aliase

  • readal
  • statal
  • trimal

Verlauf

Projektgeschichte und Nutzung

trimAl is a bioinformatics command-line tool for automated trimming of multiple sequence alignments before phylogenetic analysis. Its package history is rooted in reproducible scientific pipelines: remove unreliable columns or sequences, then feed cleaner alignments into downstream tree-building tools.

Projektgeschichte

The trimAl documentation describes the tool as software for automatically removing spurious sequences or poorly aligned regions from a multiple sequence alignment. It can select reliable positions using gap proportion, residue similarity, consistency across multiple alignments, or manual column and sequence selections.

The official documentation cites the 2009 Bioinformatics paper 'trimAl: a tool for automated alignment trimming in large-scale phylogenetic analyses' by Capella-Gutiérrez, Silla-Martínez, and Gabaldón, establishing the tool's origin in large-scale phylogenetics rather than general text processing.

Adoptionsgeschichte

trimAl's adoption came from computational biology workflows that needed a command-line way to standardize alignment trimming across many datasets. The documentation's examples and installation flow assume shell use, compiled binaries, and repeatable invocations over input/output alignment files.

Homebrew and Nix packaging matter because biology users often need the same tools on lab Macs, Linux workstations, and cluster login nodes. Packaging `trimal`, `readal`, and `statal` makes the workflow easier to reproduce without manual source builds.

Wie es verwendet wird

The basic pattern is `trimal -in <inputfile> -out <outputfile> -<trimming_method>`. The official usage page documents supported input formats such as clustal, fasta, nexus, phylip, and pir, plus output conversion, HTML reports, statistics, backtranslation, and automated methods including `-gappyout`, `-strict`, `-strictplus`, and `-automated1`.

The algorithm documentation separates manual column selection, threshold-based trimming, overlap trimming for incomplete sequences, and automated methods. This makes trimAl useful both for quick pipeline defaults and for explicit, paper-method-style parameter reporting.

Warum Paket-Nerds sich dafür interessieren

For package nerds, trimAl is the kind of small scientific binary that keeps old-school Unix bioinformatics alive: it has named executables, stable flags, plain files in and out, and no service layer.

It is also historically relevant because its value is not novelty UI but repeatability. A package-manager install lets researchers pin a formula or derivation and rerun phylogenetic trimming methods consistently across datasets.

Zeitleiste

  • 2009: trimAl paper published in Bioinformatics for automated alignment trimming in large-scale phylogenetic analyses.
  • Current docs: Version 1.5.1 binaries and source builds are documented for Linux, macOS, and Windows.
  • Current docs: trimAl/readAl installation check uses example alignments from the dataset directory.
  • Current docs: Usage documents manual, threshold, overlap, and automated trimming methods.

Related projects

  • Related tools and concepts include readAl, statAl, multiple sequence alignment formats, phylogenetic tree reconstruction, gap/similarity/consistency scoring, and downstream maximum-likelihood or neighbor-joining workflows.

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

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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
readalExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
statalExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
trimalExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

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-08-03
Manager-Version1.5.1
Manager aktualisiert2026-06-14
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:trimal
Version1.5.1
PaketmanagerHomebrew
Homepagehttps://trimal.readthedocs.io/
Repositoryhttps://github.com/inab/trimal
Zuletzt aktualisiert2026-06-14T15:13:52+02:00
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

trimal

nix profile install nixpkgs#trimal
  • normalized package name match
  • Abgeglichen nach: Trimal
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/tr/trimal/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

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
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation