Automic VaultAutomic Vault

brew

krakend mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install krakend

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Ultra-High performance API Gateway built in Go

Verlauf

Projektgeschichte und Nutzung

KrakenD is an open-source, Go-based API gateway built around stateless, declarative configuration. Its package-manager significance comes from turning API gateway deployment into a single binary plus a JSON/YAML configuration file, rather than a heavyweight service stack.

Projektgeschichte

KrakenD's own team page says the project started in late 2016 as a library for engineers to create fast and reliable API gateways. The Community Edition repository was created on GitHub on 2017-12-03 and describes KrakenD CE as the open-source distribution of KrakenD.

The project later separated the reusable gateway engine from the product distribution. KrakenD documentation says the engine was formerly the KrakenD Framework and became the Lura Project when it joined the Linux Foundation in 2021.

Adoptionsgeschichte

KrakenD was adopted by teams using microservices and backend-for-frontend patterns because it emphasizes stateless nodes, declarative configuration, composition, rate limiting, telemetry integration, JWT/security features, and low operational overhead.

The official case-study and documentation corpus positions KrakenD as a production gateway for cloud-native and self-hosted environments, while Homebrew packaging gives developers a local CLI path for validating and running gateway configs.

Wie es verwendet wird

The normal package-manager workflow installs the krakend binary, then runs it against a configuration file commonly named krakend.json. Official docs describe /etc/krakend/krakend.json as the default container-style path and krakend.json as the simple local configuration name.

KrakenD configurations declare endpoint arrays and backend relationships, with extra_config sections used by optional components outside Lura's core behavior.

Warum Paket-Nerds sich dafür interessieren

KrakenD is interesting because it packages an API gateway as a Go CLI/server binary with config-first operations. The Lura split also makes it a visible example of a productized open-source distribution built over a reusable framework governed separately.

Zeitleiste

  • 2016: KrakenD started as a library for creating API gateways.
  • 2017-12-03: The krakend-ce GitHub repository was created.
  • 2019: KrakenD 1.0 was announced.
  • 2021: The KrakenD Framework became the Lura Project under the Linux Foundation.
  • 2022-06-15: KrakenD v2.0.5 recorded the organization rename from devopsfaith to krakend in the official changelog.

Related projects

  • Lura is KrakenD's engine and the direct framework-level related project. KrakenD also belongs to the broader API gateway ecosystem alongside products such as Kong, Tyk, and other reverse proxy or service-edge gateways.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für krakend wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhä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.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
/etc/krakend/krakend.jsonkrakend.json

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
krakendcliglobales 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-26
Manager-Version2.13.8
Manager aktualisiert2026-07-08
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.13.8

https://github.com/krakend/krakend-ce

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:krakend
Version2.13.8
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/krakend
Homepagehttps://www.krakend.io/
Repositoryhttps://github.com/krakend/krakend-ce
Upstream-Dokumentationhttps://www.krakend.io/docs
LizenzApache-2.0
Quellarchivhttps://github.com/krakend/krakend-ce/archive/refs/tags/v2.13.8.tar.gz
Zuletzt aktualisiert2026-07-08T14:28:20Z
Pulseupdated
Build-Abhängigkeitengo
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 Namekrakend
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • 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 configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment