docs: data-provider evaluations record (PR-A12 / OpenBB rejected)#178
Merged
costajohnt merged 1 commit intomainfrom Apr 26, 2026
Merged
docs: data-provider evaluations record (PR-A12 / OpenBB rejected)#178costajohnt merged 1 commit intomainfrom
costajohnt merged 1 commit intomainfrom
Conversation
Per the audit's PR-A12 spec ("Verify license first; if AGPL, document
and skip"): OpenBB is licensed AGPL-3.0. The Section 13 network-use-is-
distribution clause means linking OpenBB into alpaca-trader and
exposing it over any network surface (the Flask dashboard, Telegram
alerts) would force the entire alpaca-trader source to be released
under AGPL too. Not feasible for a personal paper-trading project.
The existing yfinance + Finnhub + EDGAR + OpenRouter stack continues
to cover the needed surfaces.
This document records the evaluation outcome plus permissively-licensed
alternatives (Tiingo, FMP, Intrinio, Benzinga) for future maintainers
who hit the same "should we adopt OpenBB?" question — saves them the
same license investigation.
License clearance also documented for the providers we already use
(yfinance Apache-2.0, finnhub-python Apache-2.0, EDGAR public-domain,
OpenRouter HTTP API).
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per the audit's PR-A12 spec ("Verify license first; if AGPL, document and skip"):
OpenBB is AGPL-3.0 (verified via
gh api repos/OpenBB-finance/OpenBB/contents/LICENSE— full text in the project's repo).AGPL-3.0 Section 13's network-use-is-distribution clause means linking OpenBB into alpaca-trader and exposing it over any network surface (the Flask dashboard at
scripts/dashboard.py:8050, Telegram alerts, etc.) would force the entire alpaca-trader source to be released under AGPL too. Not a viable trade-off for a personal paper-trading project.What's in the doc
docs/data-provider-evaluations.mdrecords:Why this matters
Future maintainers who hit "should we adopt OpenBB?" can skip the license investigation and the spike-cost — the answer is documented, with the alternatives ready to evaluate in isolation if needed.
Test plan
🤖 Generated with Claude Code