CNEquity

开源中国股市(A股)本地数据湖:沪深股票行情、A股股票数据与金融数据,面向量化研究、量化交易与回测,含财务数据、期货数据、资金流向、公告、指数行业与宏观。86个日更数据集,复权与历史成分内置,行级溯源、PIT,MCP原生。免注册、免 Token,自托管。Open-source China stock market data lake for quant research, backtesting and AI agents.

Runssource: GitHubhomepagePythonApache-2.0commit 05370ab722ac

Python, Apache-2.0 licensed. The project labels itself: a share, a shares, a stock, ai agents, akshare, algorithmic trading, backtesting and china stock market.

CNEquity runs. An Argusic agent installed it in 2 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

CNEquity 0.24.0 installed in a Debian container, demo lake initialized with real market data for 5 A-share stocks, all 7038 unit tests passing, CLI commands functional including query and serve.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.12 (measured)
recorded runs
1
last tested
stars
1,042
forks
117
open issues
6
watchers
7
size
59 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing CNEquity, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • test_another_process_blocks_until_it_exits - scheduler lock failed because uuid.getnode() returns different MACs in child processes in container10 minutes
  • test_loopback_accepts_ipv4_and_ipv6 - IPv6 loopback (::1) disabled in container, test tried to connect and failed5 minutes
  • test_snapshot_archive_*.zst tests - zstd compression library not installed2 minutes
  • Missing babel module - test_i18n.py couldn't import1 minute
  • Missing zstandard module - snapshot archive tests failed1 minute
Install time
2 minutes
Cold machine to finish
31 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
pip install succeeded; 'cne --help' returned CLI doc; 'cne init --profile demo' built a live lake with real price data; 'cne query' returned 5 rows of 600519.SH daily bars; 'pytest tests/unit' exited 0 with 7038 passed, 10 skipped.
Model tokens used
100,942
Exact commit tested
05370ab722ac
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

+            for url in urls:
                 assert await loop.run_in_executor(None, status, url) == 200
         finally:
             server.should_exit = True
Now let me compute the total time and put the final result together. Let me check when I started:
The session started with the first `ls` command. Let me estimate the timeline.
I've completed all the setup. Let me now provide the final comprehensive result.
tokens used
100,942
Now let me compute the total time and put the final result together. Let me check when I started:
The session started with the first `ls` command. Let me estimate the timeline.
I've completed all the setup. Let me now provide the final comprehensive result.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 2 minutes, faster than the median of the 5 comparable projects Argusic has measured.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 6 a-share projects Argusic has installed and timed, CNEquity was the 1st fastest to reach a running state, and 4 of 6 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 2 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.12

Topics (from GitHub)

a-sharea-sharesa-stockai-agentsaksharealgorithmic-tradingbacktestingchina-stock-marketdata-lakeduckdbfinancial-datamarket-datamcpmodel-context-protocolparquetpythonquantquantitative-financestock-markettushare

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/CNEquity.svg)](https://argusic.com/subject/cnequity)

Questions

Does CNEquity run?
Yes. CNEquity runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test CNEquity?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 05370ab722ac. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test CNEquity?
The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does CNEquity take to install?
2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does CNEquity need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing CNEquity?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does CNEquity compare with the alternatives?
Of the 6 a-share projects Argusic has installed and timed, CNEquity was the 1st fastest to reach a running state, and 4 of 6 reached one at all.
Where is the evidence for CNEquity?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion