* Drop Python 3.10 support
Python 3.10 reached end of life on 2026-10-01, and the patched releases of
Pillow (13.0.0) and filelock (>=4.2.1) require Python >=3.11, so the 3.10
resolution fork kept vulnerable versions in every lockfile.
- requires-python = ">=3.11,<4" in all pyproject.toml files, the
cookiecutter template, and the CLI codegen project template
- CI: drop the ubuntu 3.10 matrix rows, move the macOS/Windows minimum
rows and the lint jobs to 3.11, drop 3.10 from the nox sessions
- READMEs: state 3.11 as the minimum supported version
* Relock with patched certifi, filelock, virtualenv, Pillow, and fastmcp
Regenerate all 38 uv.lock files against requires-python >=3.11 and upgrade
only the packages with open Dependabot advisories:
- certifi 2026.7.22 -> 2026.10.23 (GHSA-6q48-6c7w-9gw2, compromised emSign CAs)
- virtualenv 21.14.7 -> 21.14.13
- filelock 4.1.0/4.2.0 -> 4.2.4
- Pillow 12.3.0 -> 13.0.0
- fastmcp / fastmcp-slim 4.1.0 -> 4.1.3
All other changes are removed Python 3.10-only resolution forks; no other
package changes version for Python 3.11+.
* desktop: bump zod, @hookform/resolvers, and vitest
- zod ^3.25.76 -> ^4.6.7 (GHSA-mrhx-c7xc-m3w5; no patched 3.x exists)
- @hookform/resolvers ^3.10.0 -> ^5.9.2 for zod 4 support
- vitest ^4.1.11 -> ^4.1.12 (@vitest/mocker GHSA-qxg6-89mg-rqv8,
GHSA-xp26-3454-mjgp)
- override zod to the root version so @openbb/ui-pro, which declares
zod ^3 but never imports it, does not pull in a second, vulnerable copy
* desktop: remove Python 3.10 from environment pickers
- version pickers in InstallComponents and AddExtensionSelector start at 3.11
- create_environment_from_requirements accepts 3.11 through 3.14 and falls
back to 3.12 otherwise (previously 3.10 through 3.13)
- component tests select 3.11 instead of 3.10
* Remove Python 3.10 tomli fallbacks
With requires-python >=3.11, tomllib is always available, so the
version-conditional tomli imports are dead code.
- import tomllib directly in the cli and core config loaders, the
mcp_server and platform_api config validators, dev_install.py, and
the cli and cookiecutter tests; dev_install.py no longer pip-installs
tomli on the fly
- drop the tomli>=2.0; python_version<'3.11' dependency from cli, core,
mcp_server, and platform_api, plus platform_api's backport comment
- raise the fake-extension fixtures in cli/conftest.py,
core/integration/conftest.py, and the charting test metadata to
>=3.11
- relock cli, core, mcp_server, and platform_api; only the tomli
requires-dist entry is removed and resolution markers are reordered,
no package versions change
* Target Python 3.11 in ruff and ty for cli, core, mcp_server, platform_api, cookiecutter
With ruff target-version py310 and ty python-version 3.10, both tools
reject an unconditional `import tomllib`: ty reports it as unresolved
(exit 1) and ruff's isort classifies it as third-party. Raise the targets
in the projects that now import tomllib directly, and in the root
ruff.toml that governs dev_install.py.
- ruff target-version = "py311" and ty python-version = "3.11" in cli,
core, mcp_server, platform_api, and cookiecutter; root ruff.toml
target-version = "py311"
- UP042: OutputMode, ChartLifecycle, MCPType, and HTTPMethod become
StrEnum; every consumer uses .value or == comparisons, so only str()
and format() output change
- UP017: datetime.timezone.utc -> datetime.UTC (ruff autofix) in the cli
dispatchers, the cli test generator, and a core test
* Fix ruff and ty failures in packages this PR touches
CI installs unpinned dependencies, so the lint jobs ran against
pandas 3.1.0, ruff 0.17.2, and ty 0.0.91.
- cli/conftest.py: guard the find_spec("openbb") lookup so ty no longer
reports an Optional ModuleSpec/origin (failing Lint openbb-cli)
- quantitative: pandas 3.1 types Index.max() as object; cast max_date to
Timestamp before period_start in attribution, factors, and
risk_decomposition (failing ty)
- federal_reserve: use Series(...).dt.date instead of
DatetimeIndex.date so neither pandas 3.0 nor 3.1 needs a ty: ignore
(pandas 3.1 made the existing ignores unused, failing ty)
- core tests: type the filter_by_dates doubles as Data subclasses and
cast the deliberate bad arguments in test_helpers.py; apply ruff format
to test_docstring_generator_helpers.py
- platform_api README: apply ruff format to the Python code blocks
* Fix pandas 3.1 deprecations failing fred, sec, and eia tests
These suites turn warnings into errors, and pandas 3.1.0 adds
Pandas4Warning deprecations for several patterns they use. Every change
also passes with the locked pandas 3.0.6.
- fred, sec: replace inplace=True sort_values/reset_index/rename/
set_index/drop with reassignment
- fred balance_of_payments, sec as_filed_widget: replace fillna with a
string on float columns by astype(object).where(notna, ...)
- sec: build quarter start dates from ISO strings instead of parsing
"2024Q2"-style strings; use the DataFrame constructor instead of
DataFrame.from_records for column dicts; pad CIK lookup rows to two
fields instead of constructing a ragged DataFrame
- eia: read EIA workbooks with the calamine engine (xlrd is deprecated);
replace the xlrd dependency with python-calamine and relock; calamine
workbooks are not safe for concurrent reads, so the petroleum status
report serializes its sheet reads with a lock
* imf: fall back to the published catalog when the IMF API is unreachable
imf_cache.json.xz is generated at build time and is not committed, so
every CI build of openbb-imf needed a live api.imf.org. The only fallback
was actions/cache, and caches saved by pull_request runs are scoped to
that PR, so a new PR never had one. With api.imf.org returning
"503 no healthy upstream" during IMF's data portal maintenance window,
the build failed.
When live generation fails on a non-forced build, the hook now copies
imf_cache.json.xz from the latest openbb-imf wheel on PyPI, after
checking the wheel's sha256 against the digest PyPI publishes. Builds
with OPENBB_IMF_FORCE_CACHE_REBUILD=1, which the publish workflow sets,
still fail hard, so a release never ships a stale catalog.
---------
Co-authored-by: dlee-bq <325002271+dlee-bq@users.noreply.github.com>
OpenBB Nasdaq Provider
This extension integrates the Nasdaq data into the OpenBB Platform.
Every dataset is read from the public Nasdaq website API. No API key or account is required.
This extension is not affiliated with, endorsed by, or authorized by Nasdaq, Inc.
Installation
Install from PyPI:
pip install openbb-nasdaq
Or from the source tree:
uv pip install -e openbb_platform/providers/nasdaq
Then rebuild the Python interface:
import openbb
openbb.build()
Coverage
Nasdaq publishes far more than US equities. This extension covers the US market activity API, the Nasdaq Nordic and Baltic markets, and the Morningstar fundamentals Nasdaq co-brands for Nordic listings.
US markets
| Command | Description |
|---|---|
equity.search |
The Nasdaq-traded symbol directory. |
equity.screener |
Screen US listings by exchange, sector, region, market cap, and country. |
equity.quote |
Delayed quotes with the sector, market cap, and dividend summary. |
equity.profile |
Company profile, sector, industry, and business description. |
equity.historical |
Daily OHLCV history. |
equity.filings |
SEC filings, with links to the filed PDFs. |
equity.fundamental.balance · income · cash · ratios |
Statements and ratios, annual or quarterly. |
equity.fundamental.dividends · historical_eps |
Dividend history and earnings surprises. |
equity.ownership.insider_trading · institutional · short_interest |
Ownership and short interest. |
equity.estimates.price_target · consensus |
Analyst actions and the consensus overview. |
equity.calendar.earnings · dividend · splits · ipo |
Corporate calendars. |
economy.calendar |
The economic events calendar. |
markets.status |
Session status with the next open and close times. |
markets.movers |
Most active, advancers, decliners, and Nasdaq-100, by session. |
markets.quotes |
One request for a mixed-asset watchlist. |
markets.upcoming |
Event counts and a preview of the next session. |
index.search · snapshots · historical |
The index universe, snapshots, and history at 1d or 1m. |
etf.search · info · holdings · equity_exposure · historical |
Funds, their top-ten holdings, and the reverse exposure lookup. |
crypto.historical |
Daily crypto pair history. |
options.chains |
Full chains, narrowable to one expiration for full per-contract detail and greeks. |
news.company |
Company news and press releases. |
Nasdaq Nordic and Baltic
| Command | Description |
|---|---|
nordic.screener |
19 asset classes - shares, indexes, funds, ETPs, options, custom basket forwards, corporate/government/mortgage bonds, sustainable debt, FI derivatives, structured products, warrants, and certificates. |
nordic.info |
Reference and trading metadata, plus the company profile. |
nordic.fundamentals |
Morningstar statements, ratios, growth rates, and peers. |
nordic.dividends |
Declared distributions with ex and payment dates. |
nordic.historical |
Daily prices, with duration and yield for fixed income. |
nordic.historical_trades |
Trade-by-trade history with the buying and selling members. |
nordic.movers · derivatives_volume |
Most traded instruments and derivatives market volume. |
nordic.knocked_out |
Leverage instruments whose barrier has been breached. |
nordic.bond_yields |
Average Danish bond yields by segment and residual maturity. |
nordic.index_factors |
Inflation index factors for index-linked mortgage bonds. |
nordic.mortgage_rates |
Listed mortgage rates by lender and fixed-rate term. |
nordic.trading_hours · holidays |
Session hours and the exchange holiday calendar. |
nordic.symbol_choices |
The full instrument directory, for symbol pickers. |
nordic.news |
Company announcements and exchange notices. |
Notes on the data
Asset classes are resolved behind the scenes. Nasdaq keys most endpoints by
an asset class (stocks, etf, index, mutualfunds, crypto). You pass a
symbol; the extension resolves the class from the listing directory, falling
back to a probe only for symbols the directory does not carry.
The same applies to Nasdaq Nordic, where instruments are keyed by an opaque orderbook ID and an asset class. Every listing is indexed once per process into a single directory of roughly 17,800 instruments, so the symbol alone resolves both. Nasdaq refuses pages under load by returning them empty rather than erroring, so a page that comes back empty when the listing claims more is retried - otherwise the directory would silently come up short.
etf.holdings covers mutual funds too. ETFs are served from the company
holdings endpoint and mutual funds from the fund profile.
Options chains carry the full detail. Nasdaq's chain endpoint publishes only last, change, bid, ask, volume, and open interest, and its greeks endpoint is locked to the front expiration. The remaining fields - open, high, low, previous close, sizes, contract high and low, tick, market, and the greeks for every expiration - come from the per-strike contract endpoint, which is fanned out with bounded concurrency and retried on refusal.
Some Nordic data is only on the page. The trading hours and the exchange holiday calendar are published as server-rendered tables, not through an API, so they are read out of the markup.
Nordic fundamentals come from a PDF. The JSON sections Nasdaq exposes for Morningstar fundamentals return empty. The data is published only in the co-branded fact sheet, which this extension parses from glyph positions - the two-column layout interleaves the reading order, so plain text extraction is unusable.
Responses are cached on disk. A SQLite-backed HTTP cache holds responses with a TTL per endpoint family - sixty seconds for quotes and movers, up to a day for statements and filings - so a repeat options chain does not re-fetch thousands of unchanged contracts.
Standalone usage
The extension registers its own router, so installing openbb-nasdaq alone
still exposes every dataset under /nasdaq. Each namespace registers its
model-backed commands only when the OpenBB extension that normally owns those
standard models is absent; when openbb-equity is installed, for example, the
equity models are served through it instead and Nasdaq's own routes step aside.
The fetchers can also be used directly, independent of the Python and API interfaces:
from openbb_nasdaq import nasdaq_provider
nasdaq_provider.fetcher_dict
OpenBB Workspace
A bundled dashboard is served at /api/v1/nasdaq/apps.json, with the widget IDs
resolved against whichever extensions are installed. Start the API and add it as
a Workspace backend:
openbb-api
The app carries tabs for earnings, dividends, calendars, the economy, screeners, options, funds, indexes, and the Nordic markets. Clicking a symbol in a screener, mover, or snapshot table drives the linked widgets in that tab.
Development
uv pip install -e '.'
uv pip install --group dev
pytest tests --cov=openbb_nasdaq --cov-report=term-missing
The unit suite runs entirely offline - no cassettes and no network. Integration tests hit the live endpoints and are excluded by default:
pytest integration -m integration
OpenBB Documentation
OpenBB Platform documentation is available here.
OpenBB Workspace documentation is available here.