Automic VaultAutomic Vault

brew

fern-api mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install fern-api

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Stripe-level SDKs and Docs for your API

Verlauf

Projektgeschichte und Nutzung

Fern is an API tooling platform and CLI that turns API definitions into SDKs and documentation. The repository README describes support for OpenAPI, AsyncAPI, Protobuf, and OpenRPC, with generated SDKs in languages such as TypeScript, Python, Java, Go, Ruby, PHP, C#, Swift, and Rust.

Projektgeschichte

The public Fern repository was created in April 2022, and the `fern-api` npm package was also created in April 2022. Early package history shows rapid 0.0.x CLI publication, while the repository later grew into a monorepo containing CLI code, generators, documentation assets, and platform tooling.

By 2026 the package had moved into the 5.x release line, with Homebrew packaging `fern-api` and npm publishing frequent CLI releases. The README frames Fern as a docs-and-SDK workflow rather than only a code generator: users initialize a `fern/` directory, configure generators, and run the CLI to produce SDKs and docs.

Adoptionsgeschichte

Fern's adoption story is tied to API-first developer experience teams that want SDKs and documentation from one source of truth. The README points to public documentation sites built with Fern, including ElevenLabs, LaunchDarkly, and Hume AI, which supports a narrative of production use beyond toy examples.

The npm package is the primary CLI distribution channel, while Homebrew gives macOS and Linux users a package-manager-native install path. That combination fits the modern API-tooling pattern where Node-based CLIs are also wrapped for Homebrew users who prefer OS-level package workflows.

Wie es verwendet wird

Typical use starts with `fern init --openapi`, which creates a `fern/` directory containing `fern.config.json`, `generators.yml`, and API definition files. Users then run commands such as `fern check`, `fern add`, and `fern generate`; local generation can run through Docker with `fern generate --local`.

Fern is used when an API team wants generated client SDKs, reference documentation, hosted docs, and related developer-experience features to track the API specification. Its package history matters because the CLI is the local entry point to a larger hosted and generator ecosystem.

Warum Paket-Nerds sich dafür interessieren

For package maintainers, Fern is a fast-moving Node-distributed CLI whose Homebrew formula follows npm release cadence. That makes it part of the modern class of API development tools where the package is small from the user's perspective but fronts a larger cloud and generator platform.

Fern is also notable because its CLI repository documents both generated artifact workflows and the project's own reproducible development setup through DevBox, reflecting the packaging concerns of a polyglot generator stack.

Zeitleiste

  • 2022: Public GitHub repository and npm package created.
  • 2023: Repository README identifies Fern as a Y Combinator 2023 startup.
  • 2026: npm and Homebrew package metadata show the CLI in the 5.x release line.

Related projects

  • Fern belongs to the API specification and SDK generation ecosystem alongside OpenAPI, AsyncAPI, Protobuf, OpenRPC, AWS Smithy, Palantir Conjure, and Stripe-style developer documentation workflows.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für fern-api 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.
  • Installiert mit 1 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.

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
fern/fern.config.jsonfern/generators.yml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ferncliglobales 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-25
Manager-Version5.80.0
Manager aktualisiert2026-07-23
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://buildwithfern.com/

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:fern-api
Version5.80.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/fern-api
Homepagehttps://buildwithfern.com/
Repositoryhttps://github.com/fern-api/fern
Upstream-Dokumentationhttps://buildwithfern.com/learn
LizenzApache-2.0
Quellarchivhttps://registry.npmjs.org/fern-api/-/fern-api-5.80.0.tgz
Zuletzt aktualisiert2026-07-23T16:18:57Z
Pulseupdated
Abhängigkeitennode
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 Namefern-api
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 configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment