meixuesong/aggregate-persistence-sample

This is a Java-based order management system built with Spring Boot and MyBatis. It provides APIs for creating, updating, and checking out orders, utilizing selective updates to optimize database interactions. The codebase includes comprehensive integration tests to verify the order lifecycle and is structured using Maven for dependency and build management.

Introduces a complete order management feature, including an OrderController, OrderService, and OrderFactory to handle creating, updating, and checking out orders. The implementation uses MyBatis for data access, featuring a key behavioral change: order and order item updates are performed selectively, updating only the changed fields rather than the entire record, which improves efficiency and supports optimistic locking via versioning.

src/main · high confidence

Added new test classes, including a base \ApiTest\ and specific tests for the \OrderController\, to verify order creation, updates, item modifications, and checkout processes.

src/test · high confidence

Added a Maven (pom.xml) build file for the aggregate-persistence sample project, establishing the project structure and dependencies. This includes Spring Boot 2.6.2, aggregate-persistence 1.2.3, Spring Boot starters for JDBC, JPA, and Web, MyBatis (2.1.0), MyBatis Generator (1.3.7/1.3.6), Lombok (1.18.6), and H2 for testing. The configuration also sets up the Spring Boot Maven plugin, MyBatis Generator plugin, and release-profile plugins (Nexus staging, source/javadoc/GPG signing, JaCoCo, and maven-source/javadoc plugins).

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 58 → 59 (+1.2)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (+0.0)
• Architecture 69 → 69 (+0.0)
• Maturity 63 → 63 (+0.0)
• Readiness 39 → 46 (+6.3)
• Security 100 → 78 (-22.2)
• Domain Modelling 100 → 100 (-0.0)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• No exposed public API
• Scanner failed to run — not a clean result
• Test reliability not included
• early-stage repository — too few commits for a meaningful bus factor
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• git history depth insufficient

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• No SBOM
• No build provenance
• No dependency advisory monitoring
• Scanner failed to run — not a clean result
• Scanner failed to run — not a clean result

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

meixuesong/aggregate-persistence-sample was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.