Automic VaultAutomic Vault

brew

badread mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install badread

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Long read simulator that can imitate many types of read problems

Befehle und Aliase

  • badread

Verlauf

Projektgeschichte und Nutzung

Badread is a bioinformatics CLI for simulating error-prone long sequencing reads. It is historically notable less as a large software platform and more as a citable research tool that gave developers controlled ways to stress-test long-read assemblers and analysis pipelines.

Projektgeschichte

The Badread GitHub repository was created in June 2018, with the first v0.1.0 GitHub release in July 2018. The README says Badread was made to test tools that take long reads as input by letting users control read problems such as chimeras, low-quality regions, systematic basecalling errors, junk reads, random reads, adapters, glitches, and quality-score models.

Badread was published in the Journal of Open Source Software in 2019 as 'Badread: simulation of error-prone long reads' with DOI 10.21105/joss.01316. That gave the package a stable academic citation path alongside its command-line distribution.

The project continued to track long-read practice in later releases, with README examples for older Oxford Nanopore reads, newer Nanopore R10.4.1-style settings, PacBio HiFi-style reads, and configurable error and qscore models.

Adoptionsgeschichte

Badread's adoption is mainly in computational biology workflows where developers need reproducible fake FASTQ data. Its packaging in Homebrew makes it easy for macOS bioinformatics users to install without manually cloning the repository, while the README also documents pip installation directly from GitHub.

The JOSS publication and Zenodo DOI made Badread easier to cite in papers and benchmarking notes than many informal simulator scripts. GitHub release activity from 2018 through 2026 shows a maintained niche tool rather than a frozen paper artifact.

Wie es verwendet wird

Typical usage is badread simulate with a reference FASTA and requested quantity, piping FASTQ output through gzip. Users tune read length, identity, error model, qscore model, adapter sequences, chimeras, glitches, junk reads, random reads, and seeds.

The README emphasizes control over realism: users can deliberately make reads very bad, pretty good, very good, or platform-like in order to test how downstream tools react.

Warum Paket-Nerds sich dafür interessieren

Badread matters to package nerds because it is a compact example of research software that deserves normal CLI packaging: it has a paper, DOI, reproducible command-line interface, domain data models, and a long tail of users who may just need the executable in a workflow.

It also shows why scientific packages often live awkwardly between GitHub, pip, Homebrew, and citation systems: the code, docs, releases, and scholarly identity all matter.

Zeitleiste

  • 2018: Badread GitHub repository created and v0.1.0 released.
  • 2019: Badread published in the Journal of Open Source Software.
  • 2021: v0.2.0 released.
  • 2023: v0.3.0 and v0.4.0 released.
  • 2026: v0.4.2 released.

Related projects

  • Badread is related to long-read sequencing platforms and models such as Oxford Nanopore and PacBio.
  • The README compares Badread with other long-read simulators and notes dependencies such as Edlib, NumPy, SciPy, and Matplotlib.

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 3 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
badreadcliglobales 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-Version0.4.2
Manager aktualisiert2026-04-22
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.4.2

https://github.com/rrwick/Badread

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:badread
Version0.4.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/badread
Homepagehttps://github.com/rrwick/Badread
Repositoryhttps://github.com/rrwick/Badread
Upstream-Dokumentationhttps://github.com/rrwick/Badread#readme
LizenzGPL-3.0-or-later
Quellarchivhttps://github.com/rrwick/Badread/archive/refs/tags/v0.4.2.tar.gz
Zuletzt aktualisiert2026-04-22T09:09:57Z
Pulseupdated
Abhängigkeitennumpy, python@3.14, scipy
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 Namebadread
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

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
  • package relationship graph
  • package version freshness
  • package-page enrichment