Automic VaultAutomic Vault

brew

Install fern-api with Homebrew

Stripe-level SDKs and Docs for your API. Version 5.66.0 via Homebrew; verified 2026-07-08.

install

Additional install commands

macOS

Homebrewverified ยท 100%
brew install fern-api

local Homebrew formula metadata

overview

Package summary

Stripe-level SDKs and Docs for your API

Commands and aliases

  • fern

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

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

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for fern-api. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

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

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

Installed executables

CommandKindExposureNote
ferncliglobal executable

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-07-08
manager version5.66.0
manager updated2026-07-08
local dataok
upstreamnot checked
latest detectednot detected

https://buildwithfern.com/

install metadata

Package metadata

Package keybrew:fern-api
Version5.66.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/fern-api
Homepagehttps://buildwithfern.com/
Repositoryhttps://github.com/fern-api/fern
Upstream docshttps://buildwithfern.com/learn
LicenseApache-2.0
Source archivehttps://registry.npmjs.org/fern-api/-/fern-api-5.66.0.tgz
Last updated2026-07-08T03:27:46Z
Pulseupdated
Dependenciesnode
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

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