pkg.soopen package index

brew / rank 6427

Install trimal with Homebrew, Nix

Automated alignment trimming in large-scale phylogenetic analyses. Version 1.5.1 via Homebrew; verified 2026-06-14. Also installable with nix: nix profile install nixpkgs#trimal.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install trimal

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#trimal

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

overview

Package summary

Automated alignment trimming in large-scale phylogenetic analyses

Commands and aliases

  • readal
  • statal
  • trimal

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
readalexecutableindexed executableDiscovered from the local executable index.
statalexecutableindexed executableDiscovered from the local executable index.
trimalexecutableindexed executableDiscovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version1.5.1
manager updated2026-06-14
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:trimal
Version1.5.1
Package managerHomebrew
Homepagehttps://trimal.readthedocs.io/
Repositoryhttps://github.com/inab/trimal
Last updated2026-06-14T15:13:52+02:00
Pulseupdated
Bottlenot recorded
Servicenone declared

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

trimal

nix profile install nixpkgs#trimal
  • normalized package name match
  • Matched by: 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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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