Skip to content

Ecosystem architecture and boundaries

This diagram describes repository and runtime responsibilities. It does not imply that every node is a stable release; check the catalog for status.

Verified boundaries

  • The public organization currently contains only its profile and this Pages site, with no installable Java utility library.
  • This organization does not present Alibaba EasyExcel, Dromara Sa-Token, or Hutool as its own work.
  • Any future project must document its upstream differences, maintenance boundary, test evidence, and Maven Central release plan.

Suggested reading order

  1. Find the entry point closest to your use case in the diagram.
  2. Confirm whether the repository is public, a private preview, or archived.
  3. Open its README and confirm API, version, tests, and license.
  4. Run the smallest verification from Getting Started before business integration.

Last updated: