macrozheng/mall

Choose this fork only if you want a legacy, customized mall codebase with extra docs/schema materials and can live without current upstream maintenance. If you want an actively maintained starter, newer Java/Spring support, or easier adoption, upstream is the better default.

Choose this fork if you need a customized mall baseline with WeChat/app-oriented changes and can accept significant drift from upstream. Prefer upstream if you value current maintenance, broader compatibility, and lower integration risk.

Choose this fork if you want a packaged, documentation-heavy mall snapshot and are comfortable owning the maintenance gap. Choose upstream if you need current fixes, newer platform support, and a lower-risk long-term base.

Choose this fork only if you specifically want an older, customized mall codebase and are willing to own the gap to upstream. For most adopters, upstream is the better starting point because this fork is stale, significantly diverged, and has removed or weakened some core integrations.

Prefer this fork only if you want a frozen, highly customized mall baseline and are willing to maintain it yourself. If you want an actively maintained reference project or an easy upstream sync path, the upstream repository is the better choice.

Choose this fork if you want a customized mall snapshot with extra documentation and deployment material. Avoid it if you need a current, maintainable base or expect easy upstream syncing, because it is significantly behind and appears stale.

Prefer upstream if you want an actively maintained reference mall platform. Prefer this fork only if its POS-oriented/customized workflow matches your target and you are comfortable inheriting a stale, significantly diverged codebase with removed payment-related functionality.