HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wilsonfreitas
awesome-quant
HTML2019–2024
wilsonfreitas / awesome-quant

awesome-quant

A curated list of insanely awesome libraries, packages and resources for Quants (Quantitative Finance)

6Distinct people
9Mentions
0Explicit recommenders
30.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A curated list of insanely awesome libraries, packages and resources for Quants (Quantitative Finance)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2019-02-08 05:57:37 UTC to 2024-02-03 23:10:07 UTC.

01232019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC312
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202

What Hacker News says

9 sources
No, it looks more like a Rust equivalent of libraries like ffn (financial functions for python) or many of the other ones listed here https://github.com/wilsonfreitas/awesome-quant Using rust to do exploratory analysis in python seems like a misguided idea. But using rust to productize models that have performance and accuracy sensitivities, the things that C/C++ is still used for, indeed sounds like a good idea. Most of the python libraries used in finance, like numpy/pandas, call out to C for performance reasons; the libraries are essentially python bindings + syntax to C functions. It would be interesting to think about replacing that backend with rust.
In RustQuant: A Library for Quantitative Finance
The S&P500 is a backtesting reference benchmark. You can compare portfolio performance through drawdown periods with backtesting tools. Macroeconomic drawdowns are good times to have cash for acquisitions; instead of free government cheese. "Tear Sheets: Definition and Examples in Finance, Vs. Prospectus" https://www.investopedia.com/terms/t/tearsheets.asp : > While tear sheets date back to the old days when stockbrokers would rip individual pages out of the S&P summary book and send them to current or potential clients, most information is extracted online today. Therefore, any concise representation of a company's business fundamentals could be considered a tear sheet. From https://news.ycombinator.com/item?id=24428206#24429801 : > pyfolio.tears.create_interesting_times_tear_sheet measures algorithmic trading algorithm performance duri
Read the rest
ng "stress events" https://github.com/quantopian/pyfolio/blob/4b901f6d73aa02ceb... : >> Generate a number of returns plots around interesting points in time, like [...] From https://news.ycombinator.com/item?id=19111911 : > pyfolio/examples/zipline_algo_example.ipynb: https://nbviewer.org/github/quantopian/pyfolio/blob/master/p... > "Worst Drawdown Periods" Drawdown > Trading definitions: https://en.wikipedia.org/wiki/Drawdown_(economics)#Trading_d... awesome-quant > Python > Trading & Backtesting: https://github.com/wilsonfreitas/awesome-quant#trading--back... S&P500: https://en.wikipedia.org/wiki/S%26P_500
In Buffett once bet $1M that he could beat a group of hedge funds over 10 years
Is it possible to factor (e.g. GRI) sustainability criteria into the portfolio fitness function? https://news.ycombinator.com/item?id=21922558 My concern is that - like any other portfolio optimization algorithm - blindly optimizing on fundamentals and short term returns will lead to investing in firms who just dump external costs onto people in the present and future; so, screening with sustainability criteria is important to me. From https://news.ycombinator.com/item?id=19111911 : > awesome-quant lists a bunch of other tools for algos and superalgos: https://github.com/wilsonfreitas/awesome-quant
In Show HN: Eiten – open-source tool for portfolio optimization
Is there something like that, but with more predictable languages like Rust[1], or OCaml? I wouldn't trust my money for dynamic typing. I recently asked the same question[2] to the Futu broker[3]. Sadly no answer. I wish more quant companies would pay attention to the predictability of their own code and external APIs. For example using Imandra[4] to reason about their own code. Using their own protocol language specification[5] they created verified FIX library[6]. P.S. Also you might want to add that framework in Awesome Quant list[7]. [1] https://internals.rust-lang.org/t/proposal-business-applicat... [2] https://github.com/FutunnOpen/futu-api-doc/issues/2 [3] https://www.futu5.com/en/ [4] https://imandra.ai/ [5] https://docs.imandra.ai/ipl/ [6] https://docs.imandra.ai/fix-engine/ [7] https://github.com/wilsonfreitas/awesome-quant
In Gryphon: An open-source framework for algorithmic trading in cryptocurrency
> How well does it do in production though and what happens when multiple algos execute the same trades? Price inflation. > Does it cause the rest of the algos to adapt and change results? Trading index ETFs? IDK > It makes sense to back-test together and work on it, but if it's proven to work, someone will create something to monitor volume on those trades and work against it. Why does it need to do lots of trades? Is it possible for anyone other than e.g. SEC to review trades by buyer or seller? > I'd be curious to see the same algo do 300% in production, and if so, then my bias would be uncalled for. pyfolio does tear sheets with Zipline algos: pyfolio/examples/zipline_algo_example.ipynb https://nbviewer.jupyter.org/github/quantopian/pyfolio/blob/... alphalens does performance analysis of predictive factors: alphalens/examples/pyfolio_
Read the rest
integration.ipynb https://nbviewer.jupyter.org/github/quantopian/alphalens/blo... awesome-quant lists a bunch of other tools for algos and superalgos: https://github.com/wilsonfreitas/awesome-quant What's a good platform for paper trading (with e.g. zipline or moonshot algorithms)?
In Superalgos and the Trading Singularity

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.