Automic VaultAutomic Vault

brew

little-cms2 mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install little-cms2

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Color management engine supporting ICC profiles

Befehle und Aliase

  • jpgicc
  • linkicc
  • psicc
  • tificc
  • transicc

Verlauf

Projektgeschichte und Nutzung

Little CMS 2 is the second-generation line of Little CMS, an open source color management engine for ICC profile transforms. It is one of the quiet infrastructure libraries behind image editors, print pipelines, cameras, RIPs, monitors, scientific tools, and Linux desktop color management.

Projektgeschichte

Little CMS was created by Marti Maria and first released in 1998. The project set out to be a small-footprint, accurate C color management module using International Color Consortium profiles, at a time when color management was often proprietary or bundled into large graphics systems.

The project's GitHub README describes Little CMS as a full implementation of ICC specification 4.4 with support for V2 and V4 profiles, including abstract, devicelink, and named-color profiles. The modern repository was created on GitHub on February 8, 2010 and contains the Little CMS 2 codebase, documentation, utilities, tests, and build systems.

Adoptionsgeschichte

The Little CMS maintainers describe the library as widely deployed in production projects across printer firmware, monitors, digital cameras, RIPs, publishing, scientific applications, and many Linux distributions. The project website gives a coarse estimate of 50 million to 200 million installations worldwide for the CMM color engine.

Its adoption is partly invisible: users encounter Little CMS through applications and operating-system packages rather than invoking it directly, while developers pull it in for standards-based ICC transforms without building a color engine themselves.

Wie es verwendet wird

The Homebrew package installs command-line tools such as jpgicc, tificc, psicc, transicc, and linkicc, alongside the library used by applications. Those tools expose profile conversion, inspection, and linking workflows useful to graphics and print pipelines.

The library is used when software needs deterministic conversion between device profiles, RGB/CMYK/Lab spaces, proofing transforms, or ICC V2/V4 compatibility without depending on a platform-specific color stack.

Warum Paket-Nerds sich dafür interessieren

little-cms2 is a classic package-manager dependency: small, old, security-relevant, C-based, and transitively important to many media applications. It is the kind of formula users rarely install by name but often have in their dependency graph.

The package is also notable because it tracks a real-world standards domain. Its usefulness depends on ICC conformance, file-format edge cases, and security hardening around untrusted profiles, not on a flashy user interface.

Zeitleiste

  • 1998: Initial Little CMS release.
  • 2005: ICC specification ISO 15076-1 was approved as an International Standard, a standards context cited by the project README.
  • 2010-02-08: The mm2/Little-CMS GitHub repository was created.
  • 2026-04-17: The Little CMS site announced Little CMS 2.19.
  • 2026-05-06: The GitHub repository listed Little CMS 2.19.1 as a release.

Related projects

  • Related color-management projects and domains include ICC profiles, lcms command-line utilities, Linux desktop color management, Argyll CMS, image editors, print RIP software, and applications that embed Little CMS for profile transforms.

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 2 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
jpgicccliglobales Executable
linkicccliglobales Executable
psicccliglobales Executable
tificccliglobales Executable
transicccliglobales 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.19
Manager aktualisiert2026-04-24
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://www.littlecms.com/

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:little-cms2
Version2.19
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/little-cms2
Homepagehttps://www.littlecms.com/
Repositoryhttps://github.com/mm2/Little-CMS
Upstream-Dokumentationhttps://github.com/mm2/Little-CMS/tree/master/doc
LizenzMIT
Quellarchivhttps://downloads.sourceforge.net/project/lcms/lcms/2.19/lcms2-2.19.tar.gz
Zuletzt aktualisiert2026-04-24T21:23:08Z
Pulseupdated
Abhängigkeitenjpeg-turbo, libtiff
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 Namelittle-cms2
Aliases
  • lcms2
Version Scheme1
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