aimeos/aimeos

Aimeos is a strong, mature Laravel e-commerce distribution with a clear value proposition: a full shop/marketplace/B2B platform that stays close to the Laravel ecosystem while offering serious scale-oriented features such as JSON:API, GraphQL admin support, multi-vendor, multi-channel, multi-warehouse, subscriptions, RTL, many payment gateways, and large-catalog positioning. The repository looks credible from the outside: roughly 5.4k stars, 300+ forks, an MIT license, security policy, active dependency maintenance, and recent commits through April 2026. The README is unusually useful for first-time evaluation because it explains the difference between this standalone app, the headless distribution, and the Laravel package, then gives concrete installation, frontend, backend, multi-language, multi-routing, and multi-vendor setup notes.

The project structure is familiar for Laravel developers, with app, config, database, routes, resources, public, packages, and tests, plus Composer, Vite, PHPUnit, Docker Compose, and Laravel tooling. I especially like that composer.json includes post-create setup scripts for key generation, migration, setup, account creation, and success messaging, which lowers the barrier for someone trying the project quickly. PHPUnit is configured for both unit and feature test suites, and coverage includes ./app, so the project at least gives contributors an expected test entry point.

The biggest improvement opportunity is contributor confidence. The GitHub Actions page appears to show the generic Actions onboarding screen rather than visible repository workflows, so it is not obvious whether PRs run automated tests in GitHub. For an e-commerce platform, adding visible CI for Composer install, PHPUnit, Pint/style checks, and frontend build would make the maintenance story much stronger.

I would also tighten the README’s polish: there are small spelling issues like “Extremly,” “multi-tentant,” and “Completly,” and the performance claims would be more persuasive if linked to benchmark methodology. Finally, the repo has only a few open issues, which is good, but one dates back years; either closing stale questions or documenting why they remain open would improve the project’s support signal.