install

Additional install commands

macOS

Homebrewverified · 100%

brew install openliberty-microprofile4

local Homebrew formula metadata

overview

Package summary

Lightweight open framework for Java (Micro Profile 4)

Project links

Homepage

Commands and aliases

openliberty-microprofile4

history

Project history and usage

openliberty-microprofile4 is the Homebrew Open Liberty distribution aimed at Eclipse MicroProfile 4.0 workloads. It packages the same Open Liberty runtime lineage around the MicroProfile API set for cloud-native Java services rather than around the full Jakarta EE platform.

Project history

Open Liberty was open sourced by IBM in 2017 from Liberty, a runtime IBM started in 2012 for small footprint, modular configuration, and flexible Java deployment. The project has since acted as IBM's open implementation base for Jakarta EE and Eclipse MicroProfile and as the foundation for WebSphere Liberty.

MicroProfile emerged to standardize APIs common in Java microservices. Open Liberty's `microProfile-4.0` feature combines Liberty support for Eclipse MicroProfile 4.0 for Cloud Native Java and includes capabilities such as Config 2.0, Fault Tolerance 3.0, Health 3.0, Metrics 3.0, OpenAPI 2.0, OpenTracing 2.0, and Rest Client 2.0.

Adoption history

Open Liberty has long used MicroProfile as part of its cloud-native positioning: enterprise Java teams could run a smaller set of service-oriented APIs without enabling a whole Jakarta EE platform. MicroProfile 4.0 aligned with Jakarta EE 8, which made it a useful bridge for organizations already standardized on Java EE 8 APIs while adopting microservice conventions.

A MicroProfile-specific package is attractive to developers and operators who care about the exact API bundle available on disk. It separates the microservice profile from Open Liberty's Jakarta EE full-platform and Web Profile packages.

How it is used

In a Liberty server, the MicroProfile 4.0 convenience feature is enabled with `<feature>microProfile-4.0</feature>` in `server.xml`. That enables CDI, JAX-RS, JSON-B, JSON-P, Servlet, and the MicroProfile APIs used for externalized configuration, health endpoints, metrics, OpenAPI descriptions, fault tolerance, tracing, JWT, and REST clients.

Developers use this runtime for local service development, CI checks, and deployment packaging where the application expects MicroProfile 4 behavior. The same Open Liberty ecosystem also offers Maven and Gradle plugins, container images, and IDE tooling for iterative dev mode.

Why package nerds care

This formula is notable because it tracks an API profile, not just an upstream release train. Package managers that expose Open Liberty by MicroProfile level let users install a runtime whose compatibility promise is visible in the package name.

It also captures the enterprise Java split between platform profiles and microservice profiles: `openliberty-microprofile4` overlaps with Jakarta EE components but exists for a different operational story.

Timeline

2012: Liberty began inside IBM as a lightweight runtime.
2017: IBM opened Liberty development as Open Liberty on GitHub.
2021: MicroProfile 4.0 aligned with Jakarta EE 8 and was documented in Open Liberty tutorials and feature references.
Open Liberty documentation defines `microProfile-4.0` as the convenience feature for Eclipse MicroProfile 4.0 for Cloud Native Java.

Related projects

Related technologies include Eclipse MicroProfile, Jakarta EE 8, Open Liberty's MicroProfile feature family, WebSphere Liberty, and the Open Liberty Maven and Gradle plugins.

Sources

security posture

No protected-tool coverage found yet

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

Install behavior

No Homebrew bottle metadata was recorded.

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: ${wlp.user.dir}/servers/${wlp.server.name}/server.xml${wlp.user.dir}/servers/${wlp.server.name}/bootstrap.properties${wlp.user.dir}/servers/${wlp.server.name}/server.env${wlp.user.dir}/servers/${wlp.server.name}/jvm.options

executables

Installed executables

Command	Kind	Exposure	Note
`openliberty-microprofile4`	executable	indexed executable	Discovered from the local executable index.

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-08-03

manager version26.0.0.7

manager updated2026-07-30

local dataunknown

upstreamnot available

latest detectednot detected

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:openliberty-microprofile4
Version	26.0.0.7
Package manager	Homebrew
Homepage	https://openliberty.io
Last updated	2026-07-30T10:53:33+09:00
Pulse	updated
Bottle	not recorded
Service	none declared

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

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.

Combined YAML source

View the package source record on GitHub.

combined/openliberty-microprofile4.yml

Used sources

Geiger risk classifier
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
pkg.so package database
pkgdb category and tag curation

Install openliberty-microprofile4 with Homebrew