mrkeyoor.comAsk

microsoft/qlibtested 03 Oct 2026commit be72549

qlib review

Our npm run installed 75 packages in 12 seconds but never installed or tested Qlib's Python platform, so the green setup result only proves its commit-check tooling is tidy.

  • 75 packages
12 sto install
    Dataevaluationupdated 04 Oct 2026
    +150stars / 7d

    Qlib is a Python platform for researching quantitative investment ideas with market data, machine-learning models, backtests, portfolio analysis, and order execution. It gives researchers one workflow for moving from a signal experiment to a recorded trading simulation, but it does not supply investment-grade data or prove that a strategy will make money.

    Verdict

    Our npm run installed 75 packages in 12 seconds but never installed or tested Qlib's Python platform, so the green setup result only proves its commit-check tooling is tidy. Use Qlib if you need an integrated quant research workflow and can own the data, Python environments, and validation of financial calculations. Do not treat the examples or a successful root npm install as production readiness.

    We ran it

    Lab card: what happened when we ran qlib
    Lab card from our sandbox run
    Screenshot of qlib (qlib.readthedocs.io/en/latest)
    qlib.readthedocs.io/en/latest
    Install✓ · 12s75 packages · 62 MB
    Buildn/ano build script
    Testsn/ano test script
    Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
    Repo626 files~75,401 lines of source · 8.2 MB · 6 CI workflows · Dockerfile · tests dir

    Answers from our run

    Does qlib build from source?

    Dependencies installed in 12 seconds (75 packages), and the project has no separate build step. We cloned commit be72549 into a clean Debian container with 3 CPUs and no project-specific setup.

    Does qlib have tests you can run?

    Not through a standard command: the project exposes no test script or target that our harness could run.

    Does qlib have known vulnerabilities in its dependencies?

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

    Who should not use qlib?

    Developers expecting the root npm install to set up Qlib: package.json only contains commit-title tooling, while the product itself is Python.

    What are the alternatives to qlib?

    Zipline, Backtrader, vectorbt. Our npm run installed 75 packages in 12 seconds but never installed or tested Qlib's Python platform, so the green setup result only proves its commit-check tooling is tidy.

    Setup2/5Root npm succeeds, but real Python and data setup is separate
    Docs4/5Detailed workflows, with candid platform and data warnings
    Community5/549,127 stars and active issues and PRs in September 2026
    Maturity3/5Broad platform, but open risk-metric and environment defects remain

    Discussed on

    1. hnQlib is an AI-oriented quantitative investment platform5 points
    2. hnOpen-source AI-oriented quantitative investment platform3 points
    3. hnQlib – an AI-oriented quantitative investment platform3 points

    Who it’s for

    Quant researchers who want data handling, model training, backtesting, and portfolio analysis in one Python project.
    Teams comparing several forecasting models against the same dataset and experiment records.
    Engineers prepared to supply, clean, and check their own market data.
    Researchers who need supervised learning, reinforcement learning, or changing-market examples rather than a small backtesting library.

    Who it’s NOT for

    Developers expecting the root npm install to set up Qlib: package.json only contains commit-title tooling, while the product itself is Python.
    Traders who need an official ready-to-use dataset: the README says Microsoft's dataset is temporarily disabled and points to a community release instead.
    Teams treating example results as investable evidence: the README warns that its Yahoo Finance data may be imperfect and recommends preparing higher-quality data.
    Production risk systems that cannot inspect open calculation defects: issue 2358 shows first-period losses can be omitted from max drawdown at commit be72549.
    Users wanting one uniform model environment: the README says benchmark dependencies differ, including an older TFT example tied to Python 3.6 or 3.7.

    Setup reality

    Our sandbox treated commit be72549 as Node because its root package.json defines npm tooling. That install succeeded in 12 seconds, adding 75 packages and using 62 MB. There was no npm build or test target, so both steps were skipped; npm audit reported 0 known vulnerabilities.

    That successful npm install does not install the Python product. Qlib itself requires Python 3.8 through 3.12, and the source route starts with NumPy and Cython. A usable workflow also needs market data, a region, model configuration, and optional analysis dependencies.

    The README recommends Conda because missing headers can break some packages. Apple Silicon users may need OpenMP for LightGBM. Microsoft's official dataset is temporarily disabled, so the quick start currently sends users to a community-maintained download or asks them to collect and validate data themselves.

    Qlib joins the research steps that usually live in separate notebooks

    Qlib covers market-data access, feature construction, model training, backtesting, portfolio analysis, and order execution. Its qrun command reads a workflow configuration and records the experiment through MLflow. That is useful when your problem is repeatability: the same dataset and evaluation path can compare LightGBM, neural models, or a custom estimator without rebuilding the surrounding machinery for each paper.

    The scope is much wider than a charting backtester. Qlib includes supervised-learning examples, changing-market research, reinforcement-learning work, online model management, and nested execution. commit be72549 contained 626 files and about 75,401 lines of source in an 8.2 MB checkout. A quant team can grow inside that structure. Someone testing one moving-average rule may spend more time learning the framework than testing the rule.

    The 12-second npm install sets up commit checks, not Qlib

    Our sandbox detected the root package.json and took the Node path. It installed 75 packages in 12 seconds and used 62 MB on disk. That package calls itself qlib-ci; its only dependencies are Commitlint packages for checking pull-request titles. A clean npm result therefore says nothing about whether Python can import Qlib, LightGBM can compile, or a sample workflow can read market data.

    This distinction is easy to miss in automated evaluations because the repository really does contain a valid Node manifest. The actual project metadata is in pyproject.toml, where pyqlib requires Python 3.8 or newer and lists data, experiment, optimization, plotting, and storage libraries. The README documents Python 3.8 through 3.12. It recommends Conda because missing headers can break installation outside a managed environment.

    What happened when we ran it

    Our run at commit be72549 installed the npm side in 12 seconds: 75 packages, 62 MB, and 0 known vulnerabilities from npm audit. No build script existed, so the lab skipped that step. No test script existed either, so it skipped tests. The repository did have 6 CI workflow files, a Dockerfile, and a tests directory, but those signals belong to the wider Python project.

    The container had 3 CPUs, 8 GB of RAM, Node 22, no secrets, and no elevated privileges. We did not run pip install, qrun, the Python tests, a backtest, or a data download. There is no honest way to turn the npm result into a claim about model speed or Python reliability. It exposed a detection trap and nothing more.

    Data ownership starts before the first backtest

    Qlib's quick start currently cannot use Microsoft's official dataset because the README says that download is temporarily disabled. It points readers to a community-maintained release, while the included collectors can build data from Yahoo Finance. The same document warns that the Yahoo data may be imperfect and recommends supplying higher-quality data. That warning matters more than the convenience of a one-command workflow.

    The offline dataset also cannot simply be extended with incremental updates because some fields were removed to make it smaller. The README tells users who need ongoing data to collect Yahoo history from scratch and then append to it. A health-check script can inspect missing values and large price or volume jumps. You still have to decide whether those thresholds fit your market, instruments, and trading calendar.

    Model breadth comes with conflicting environments

    The benchmark catalog covers many model families, but they do not share one painless environment. Qlib explicitly says each baseline has different dependencies. Its TFT example is tied to Python 3.6 or 3.7 because of TensorFlow 1.15, even though the current package supports Python 3.8 through 3.12. Reproducing an older paper may therefore mean isolating it from the main Qlib environment.

    Apple Silicon adds another documented wrinkle: LightGBM may need OpenMP installed before Qlib can build. Analysis plots are optional dependencies, and reinforcement-learning support brings Torch plus a NumPy constraint. None of these is disqualifying for a research group used to per-model environments. They do make Qlib a poor choice for a team expecting every catalog entry to run from one lockfile.

    An open drawdown bug deserves a pre-production check

    Issue 2358 reports that risk_analysis can ignore a loss in the first period when calculating maximum drawdown. Its reproduction on commit be72549 shows a series opening with a 10% loss returning a drawdown of 0. The report also traces that calculation into the standard portfolio-analysis output. For a research platform, that is a decision-relevant defect, not a cosmetic edge case.

    GitHub showed 484 open issues and pull requests, split into 305 issues and 179 pull requests when checked. The last push was September 22, 2026, and several late-September changes addressed pandas compatibility, drawdown logic, Yahoo updates, and documentation. That activity argues against calling the project abandoned. It also means adopters should pin a commit, verify the metrics they use, and read the issue queue before trusting a recorded result.

    Qlib pays off when the workflow is the product

    Choose Qlib when your team repeatedly turns market data into features, trains several models, records experiments, and evaluates strategies under one research convention. Its MIT license and broad model catalog make that a credible foundation. The price is ownership: data quality, environment isolation, and finance-specific regression checks stay with you.

    For a single strategy, Backtrader or Zipline is easier to reason about. For large vectorized parameter sweeps, vectorbt is more direct. Qlib earns its complexity when several researchers need the same path from data to analysis. Before adopting it, run the Python suite and one representative workflow on your own dataset. Our 12-second npm result cannot answer the question that matters.

    Alternatives

    ProjectWhat it isPick it when
    ZiplineA Python event-driven backtesting library descended from Quantopian's research stack.pick this instead when event-driven backtests matter more than Qlib's model and experiment pipeline.
    BacktraderA Python framework for strategy backtesting and live-trading integrations.pick this instead when you want a smaller strategy engine with broker-oriented concepts.
    vectorbtA pandas and NumPy based toolkit for fast vectorized strategy research.pick this instead when broad parameter sweeps matter more than a full ML research workflow.

    Sources

    1. Qlib README
    2. Qlib repository
    3. Qlib v0.9.7 release
    4. Issue 2358: first-period loss omitted from max drawdown

    More data reviews