ruoyi-office

🔥🔥🔥RuoYi Office 基于 SpringCloud+Vue3+Vben 的中小企业办公一体化平台,涵盖 │🏢 OA协同办公 │💼 HRM人力资源 │🤝 CRM客户管理 │📋 BPM审批流 │🛍️ ERP进销存 │📑 合同管理 │📊 PMS项目管理 │🏭 EAM资产 │📦 WMS仓储 │⚙️ MES制造执行 │💰 财务管理 │📡 IoT物联网 │🛠️ 工单管理 │🛒 MALL商城 │🤖 AI智能助手 │📈 数据报表 │等十余个子系统。

Not yet verifiedsource: GitHubhomepageJavaMITcommit ad56d726368d

Java, MIT licensed. The project labels itself: antdv, bpm, crm, eam, erp, flowable, hrm and iot.

ruoyi-office has not been verified yet.

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

At a glance

verdict
Not yet verified
Argusic Score
50 / 100
recorded runs
1
last tested
stars
502
forks
206
open issues
2
watchers
6
size
51 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 most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing ruoyi-office, 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.

  • JDK 21 cacerts trust store empty due to incomplete .deb extraction10 minutes
  • CrmContractStatusListener/CrmReceivableStatusListener: getStatus() method not found on BpmProcessInstanceStatusEvent
  • DesensitizeTest expected '芋***' but got '宇***'
  • Websocket module fails to compile without provided-scope tenant dependency
  • MySQL process killed between shell invocations preventing app launch
Install time
36 minutes
Cold machine to finish
41 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
Maven BUILD SUCCESS on yudao-server with -Pboot profile; mvn test on 4 modules passed 49/50 tests (1 pre-existing failure fixed); MySQL 8.0.46 and Redis 7.0.15 extracted and verified; DB schema imported with 59 tables; app launch blocked by process persistence issue in exec_command tool
Model tokens used
1,324,045
Exact commit tested
ad56d726368d
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

2026-10-21T16:32:25.998745Z ERROR codex_core::session: failed to record rollout items: thread 01a15…
tokens used
1,324,045
Based on my extensive work, here's the final result:
**Build succeeded** — `mvn install -DskipTests -T 1C -Pboot -pl yudao-server -am` exits with BUILD …
**Infrastructure issues prevented full app launch:** MySQL 8.0.46 and Redis 7.0.15 were both extrac…
**Errors encountered and fixed:**
1. **JDK 21 SSL truststore** — Extracted `openjdk-21-jre-headless` and `openjdk-21-jdk-headless` de…
2. **Pre-existing compilation bug** — `CrmContractStatusListener` and `CrmReceivableStatusListener`…
3. **Test bug** — `DesensitizeTest` expected `"芋***"` but the source string is `"宇擎源码"` (the first …
4. **Pre-existing websocket compilation bug** — `yudao-spring-boot-starter-websocket` had `provided…
**Tests:** Ran successfully: `yudao-common` (1 test passed), `yudao-spring-boot-starter-biz-data-pe…

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.

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/3Did not run50.000.38

Topics (from GitHub)

antdvbpmcrmeamerpflowablehrmiotlow-codemesmybatis-plusoaproject-managementsaasspringbootspringcloudvbenvue3wms

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/ruoyi-office.svg)](https://argusic.com/subject/ruoyi-office)

Questions

Does ruoyi-office run?
ruoyi-office has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test ruoyi-office?
On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
Where is the evidence for ruoyi-office?
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