mrkeyoor.comAsk

OpenBB-finance/OpenBBtested 28 Sept 2026commit 3e071fc

OpenBB review

Use OpenBB for a shared financial-data integration requirement, with acceptance checks for your exact providers and consumers.

  • Install 43 s
  • Build 0 s
189/197passed, run exited non-zero
  • 229 packages
Dataevaluationupdated 31 Oct 2026
+151stars / 7d

Choose OpenBB when several applications need access to financial data through a shared integration layer and your team can validate the results. OpenBB's Open Data Platform connects proprietary, licensed, and public data to downstream applications. Our run on September 28, 2026, at commit 3e071fc covered the CLI project, not a deployed financial-data service.

Verdict

Use OpenBB for a shared financial-data integration requirement, with acceptance checks for your exact providers and consumers. Our sandbox established installation success and unresolved CLI test failures at commit 3e071fc, not a working production deployment. Start by pinning a version, confirming its license and provider catalog, and checking one required command against source data.

We ran it

Lab card: what happened when we ran OpenBB
Lab card from our sandbox run
Screenshot of OpenBB (openbb.co)
openbb.co
Install✓ · 43s229 packages · 671 MB
Build✓ · 0s
Tests✗ · 33s189 passed · 8 failed of 197 (pytest)
Known vulns0(pip-audit)
Repo2190 files~289,320 lines of source · 239.4 MB · 16 CI workflows · tests dir

Answers from our run

Does OpenBB build from source?

Dependencies installed in 43 seconds (229 packages), and the build succeeded in 0s. We cloned commit 3e071fc into a clean Debian container with 3 CPUs and no project-specific setup.

Do OpenBB's tests pass?

No. The project's own test command finished in 33 seconds and reported 189 passed, 8 failed (pytest).

Does OpenBB have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use OpenBB?

Readers seeking proof that production provider requests work: our sandbox run did not establish that.

What are the alternatives to OpenBB?

yfinance, pandas-datareader, LEAN. Use OpenBB for a shared financial-data integration requirement, with acceptance checks for your exact providers and consumers.

Setup3/5Usable with material unresolved checks: installation succeeded in 43 seconds with a 671 MB footprint, but the test step exited 1 and the raw tail identifies CLI argument-rejection failures.
Docs4/5Broad documented support: supplied README extracts explain installation, platform surfaces, CLI modes, and backends. The rating concerns available instructions; our run did not validate every documented workflow.
Community5/5Meets the explicitly limited participation-route rubric: contributor documentation, bug reports, feature requests, feedback channels, and a merged release contribution are visible. Responsiveness, user adoption, and support quality were not measured.
Maturity4/5Broad documented integration surfaces and an observable release process support this rating. Different checkout, CLI, provider, and license states limit what the older sandbox run establishes about current deployment readiness.

Discussed on

  1. hnTell HN: OpenBB scraping GitHub emails for marketing spam190 points
  2. hnShow HN: OpenBB Terminal – Investment research for everyone182 points
  3. hnOpenBB – Open Financial Terminal4 points
  4. hnOpenBBTerminal: Investment Research for Everyone, Anywhere4 points
  5. hnOpenBB – Investment Research for Everyone, Everywhere3 points

Who it’s for

Data engineers connecting financial sources to Python, research dashboards, or AI applications.
Teams willing to check normalized financial fields against their underlying sources.
Developers prepared to pin a checkout and verify its provider catalog before adopting newer CLI documentation.

Who it’s NOT for

Readers seeking proof that production provider requests work: our sandbox run did not establish that.
Teams expecting installation success to validate data accuracy, credentials, or deployment behavior.
Analysts expecting the open-source platform to include the separate OpenBB Workspace enterprise interface.
Developers whose entire requirement fits a narrower Yahoo Finance or macroeconomic-data client.

Setup reality

Our run on September 28, 2026, tested commit 3e071fc under ./cli/ in our Python 3.12 Debian Bookworm sandbox, with 3 CPUs and 8 GB RAM. Installation succeeded in 43 seconds; the recorded dependency footprint was 229 packages and 671 MB.

The harness records each step's outcome, exit code, elapsed time, and available log tail separately from parsed test counts. Installation and build exited zero. The build duration rounded to 0 seconds in the attached summary; that does not establish that a CLI workload or deployed service worked. The test step took 33 seconds and exited 1.

The stored parser summaries record 189 passed, 8 failed, and 197 total, with no skipped tests or errors recorded. These are stored parser summaries, not verified exhaustive counts of unique tests. No new execution or complete-log reconciliation was performed for this correction.

Pip-audit recorded 0 advisories. Scan coverage is unknown: the record supplies no scannedPackages count, and its packages: 0 field does not establish how many packages were scanned.

Should you use OpenBB?

Choose OpenBB when several applications need the same financial-data integration work and your team can check the resulting fields. Its Open Data Platform connects proprietary, licensed, and public sources to downstream applications. A common integration layer is useful for that job, but our CLI run does not establish production readiness.

For a narrower requirement, compare the source you actually need. yfinance accesses Yahoo Finance data. pandas-datareader focuses on macroeconomic and factor-oriented remote data for pandas. LEAN addresses backtesting and live trading, so it can complement a data integration layer rather than replace it.

What our sandbox established

Our run on September 28, 2026, at commit 3e071fc covered the CLI project under ./cli/. Installation succeeded in 43 seconds, with a recorded footprint of 229 packages and 671 MB. That is the footprint of this checkout and installation, not a measurement of today's CLI package or every OpenBB deployment.

The harness stored step outcomes, exit codes, elapsed times, log tails, and parsed test counts. The test step exited 1 after 33 seconds. Its stored parser summaries record 189 passed and 8 failed, with 197 total; those counts do not establish exhaustive unique test coverage. The raw pytest footer separately says "8 failed, 189 passed in 28.16s". The footer's duration and the harness's elapsed step time describe different recorded timings.

Installation and build exited zero, but neither outcome proves that a provider request, REST deployment, Workspace connection, or MCP workflow succeeded. We did not establish those workloads, runtime throughput, or financial-data accuracy. This correction uses the existing record and includes no new execution.

The MrKeyoor testing methodology explains the distinction between command outcomes and workload validation. Its currently supplied version provides provenance context; it does not establish which methodology version governed this September run.

The CLI failures reached argument rejection

The raw tail identifies eight failing cases in integration/test_commands.py::test_launch_with_cli_input. They include equity history through FMP, yfinance, and Polygon; crypto, currency, futures, and ETF history through FMP; and /economy.

Each named failure ends with SystemExit: -1. The visible controller excerpt calls parse_known_args(), checks for unknown arguments, and exits when they remain. This is evidence of argument rejection in these test invocations. It does not show a provider returning bad data or refusing credentials, and the tail does not identify which arguments remained unknown.

Before adoption, repeat the commands your application needs against the pinned version. Confirm both that the CLI accepts the invocation and that the selected provider returns the expected fields. Compare a saved result with its underlying source before using it in a report or model.

Keep the tested checkout separate from current documentation

The pinned README describes OpenBB's data integration foundation and identifies Workspace as the enterprise UI. It also states that the data is not necessarily accurate. Those distinctions matter when evaluating what the repository supplies and what still needs validation.

The supplied current CLI README describes one-shot dispatch, batch requests, an interactive REPL, and pluggable backends, including generic OpenAPI 3.x servers. These are documented capabilities, not features we exercised in our older checkout. The release pull request for openbb-cli-v2.0.1 was merged into v5 on September 28, 2026; it does not identify our tested commit as that release.

Licensing also needs a version-specific check. The pinned README says AGPLv3, while the supplied current README says Apache License, Version 2.0. Our harness license signal is NOASSERTION. Check the license files for the exact version you intend to distribute instead of carrying either README statement across versions.

Choose alternatives by the work they cover

yfinance is a narrower choice for fetching Yahoo Finance data in Python. Its README describes research and educational use and says the Yahoo Finance API is intended for personal use. Check the underlying data terms before selecting it for an organizational workflow.

pandas-datareader focuses on macroeconomic, policy, and factor-style data sources for pandas. Compare it when those datasets are the whole requirement; its supplied README does not establish it as a general replacement for OpenBB's application integration surfaces.

LEAN supports backtesting and live trading algorithms. Choose it when strategy execution is the requirement. It can complement OpenBB when your system needs both data integration and a trading engine; this review did not test their interoperability.

How to read the ratings

These are editorial ratings of the supplied evidence, not benchmarks, adoption measurements, or security scores. The scale is 1 for substantial demonstrated obstacles, 2 for partial support, 3 for usable support with material unresolved checks, 4 for broad documented support with a stated limitation, and 5 for all explicitly listed criteria in that dimension. An unassessed dimension would have no numerical score.

Setup ease is 3 because installation completed but the CLI integration failures remain unresolved. Documentation is 4 because the extracts explain installation, application surfaces, and CLI modes, although their instructions were not all exercised. Community is 5 on the limited criterion of visible participation routes: contributor documentation, issue reporting, feature requests, feedback channels, and a merged release contribution are supplied. It does not rate responsiveness or adoption. Maturity is 4 for the documented integration surfaces and release process, with the checkout, provider, and license transitions requiring version-specific acceptance checks.

Alternatives

ProjectWhat it isPick it when
yfinanceA Python interface to Yahoo Finance data, described as intended for research and educational purposes.Choose it when Yahoo Finance covers the requirement and its data-use terms fit your intended use.
pandas-datareaderMacroeconomic and factor-oriented remote data access for pandas.Compare it when macroeconomic, policy, or factor-style datasets are the entire requirement.
LEAN gh↗An algorithmic-trading engine for backtesting and live trading.Choose it for strategy execution; consider it a potential complement when OpenBB supplies a separate data integration role. Interoperability was not tested.

What people are saying

  1. [velocity-scout] OpenBB-finance/OpenBB

Sources

  1. OpenBB repository and README
  2. OpenBB CLI README
  3. OpenBB CLI v2.0.1 release pull request
  4. Missing provider credential behavior report
  5. SEC standardized statements data report
  6. ODP Desktop latest stable release pointer

More data reviews