Yupe is a Yii 1 shop skeleton in Russian, still shipping a 2021 licence header

A shop engine for people who already write Yii 1

Yupe is described in the repository as an open source Yiiframework-based online e-commerce solution, and the README is written in Russian. That language choice is not incidental to the audience. The README states plainly that Yupe is primarily intended for PHP developers who are familiar with Yiiframework 1.x.

That is the whole adoption decision in one sentence. Yupe is not a shop you install and configure through a web installer with no code knowledge. It is an application skeleton for a framework, and the person deploying it is expected to read PHP.

The README also frames Yupe as more than a shop. It lists three kinds of project it is meant to create quickly: internet stores, blogs and communities, and business sites. The link for each of those goes to the same page on the project site, which is a hint that the ecommerce case is the primary one and the others are by-products of the modular structure.

The scale claim in the README is that more than 30000 projects run on Yupe, including more than 15000 internet stores, and that studios and development teams actively use it. Those are the project's own numbers, stated without a methodology, so they are best read as a claim about adoption rather than as a measurement.

The homepage is yupe.ru and there is a live demo at demo.yupe.ru, plus a chat channel, a blog, a documentation site, a team page and a contacts page.

Everything is a module, and you are meant to drop the ones you do not need

The features section of the README says that out of the box you get the skeleton of a Yii application with the functionality listed, and it adds a parenthesis that matters: everything is separated into modules, use only what you need.

The module list is long, and it is where the CMS half of the project shows. There is an internet store module with catalog, cart, orders, coupons and payment systems. There is registration, authentication and password recovery. There is user management through the admin interface, covering blocking, activation and editing. There is a blog module, for both individual and collective blogs. There is news creation and publishing, and site page management. There is category management for site sections, and site menu creation and management. There is a threaded comments module, a module of simple reference data dictionaries, a feedback module with an FAQ section, and a content blocks module.

The wiki module works through the yeeki module, and there is social network authorisation using the nodge/yii-eauth extension. The admin panel is on Twitter Bootstrap, and there is the ability to generate CRUD in a Bootstrap style.

The modularity is the interesting engineering decision here. A CMS that is also a shop, where the blog, the news, the pages, the blocks and the dictionaries are all optional pieces, is a different proposition from a shop with a bolted-on blog. The cost of that flexibility is the size of the codebase and the number of configuration decisions, which is why the README points you at asking the team when a needed feature is missing rather than at a plugin directory.

The install needs five things, and the README says five minutes

The installation process is described as very simple and taking no more than five minutes, with the instructions at the docs site. The minimum requirements for a working project are listed explicitly, and they are worth quoting as a compatibility checklist.

You need PHP 7.0 or newer, Composer, MySQL 5.x, either Apache or Nginx, and Yiiframework 1.x. The README also says that for a project to work successfully, the simplest and cheapest hosting is enough, and it recommends particular hosting providers.

Those requirements date the project precisely. PHP 7.0 and MySQL 5.x are both well past their mainstream support windows, and Yii 1 is a framework generation that the project itself is explicit about. If you are deploying this in 2026, none of those constraints are free.

The repository layout reflects a conventional Yii 1 application. There is a public/ directory for the web root, a protected/ directory for the application code, a themes/ directory for the layout and design, a vendor/ directory that is checked in, a tests/ directory with a codeception.dist.yml configuration, an img/ directory, and a read.me/ directory. There is also a build.sh script, a composer.json and composer.lock, an install.md file at the top level, and separate README.md and README_EN.md files, so an English version of the project description does exist even though the file the repository description points at is the Russian one.

The licence question has two answers in the same repository

Here is a genuine inconsistency worth flagging before you deploy anything.

The README's licence section says that the source code, design mockups and layout are distributed under the BSD licence, and it adds that the community would be grateful if a link to yupe.ru is present on the site. The copyright line reads 2012 to 2021 for yupe and the Yupe team.

The repository's own licence classification, however, is recorded as other, a custom licence that GitHub cannot classify, with the terms in the LICENSE file. And there is no LICENSE file listed in the top level entries of the repository, which include a LICENSE entry, so it does exist, but it does not obviously match a plain BSD text.

So the README describes BSD terms while the file the repository points to is something GitHub could not classify. If your use is a straightforward deployment of a shop, that difference is probably academic. If you plan to modify the code and redistribute it, or to use the design mockups, you need to read the LICENSE file and settle it, and the README request for a yupe.ru backlink is a condition you should check against as well.

The team also asks for help: the README says that if you are missing some functionality, write to them and they will definitely help. That is a reasonable arrangement for a community project, and it is also a signal that the feature set is partly shaped by requests rather than by a roadmap.

What the version history says, and what the repository holds

The release history is the clearest signal about where this project stands. The recent releases are v1.4 on 2021-09-02, 1.3 from December 2018 with the codename oriole, and 1.2 from December 2017. So the last tagged release is more than four years old.

The repository is not archived, and the last push was on 2026-09-03, so commits are still landing on master. But a push is not a release, and the two facts together describe a project where the code is touched occasionally while the published version stays where it was.

For an adopter, that distinction matters. If you install the 1.4 release you get the code as it was in September 2021. If you clone master you get something newer, untagged, with no version number to record and no release notes to read. There is a CHANGELOG.md and an UPGRADE.md in the repository, and those are the files to consult to work out what changed since 1.4 and what a migration involves.

There is also a TEAM.md file and a docs site with a team page, which is where the picture of who maintains this comes from. The repository has a .gitignore, an img/ directory, and a tests/ directory with a codeception configuration, so there is an automated test suite to run, which for a project of this size is a positive sign even though the release cadence is slow.

The 1.3 release is named for a bird, oriole. It is the kind of detail that tells you the project has a voice, which matters more than it sounds when you are deciding whether a framework generation old codebase will still be cared for in three years.

Where Yupe is the wrong choice

There are clear reasons to pass on this project, and they are not close calls.

The first is the framework. Yii 1.x is the core of the codebase, and every extension, every module and every tutorial assumes it. Starting a new project today on a framework generation that long out of support means you inherit an ecosystem where new components are not being written. That cost is not visible in the README, but it is the single biggest factor in the decision.

The second is the language of the documentation. The README, the documentation site at docs.yupe.ru and the installation guide are in Russian. There is a README_EN.md in the repository, so a machine or human translation of the overview exists, but the operational documentation, the upgrade notes and the community channels are Russian, and the chat is on Telegram. For a team that does not read Russian, the cost of finding the answer to a specific question goes up sharply.

The third is the stack. PHP 7.0 as a floor and MySQL 5.x as the database, on Apache or Nginx, with a checked-in vendor directory. That combination is a deployment in 2026 that a security team will ask questions about, and the Composer lockfile and the vendored dependencies will need attention before you go anywhere near production.

And the fourth is simply that a shop is not a small problem. Yupe gives you a great deal, and what it gives you is a 2012 to 2021 vintage PHP application with modules for everything from coupons to wiki pages. If your requirement is a small shop with a handful of products, a hosted platform is faster and cheaper. If your requirement is a large catalogue with custom behaviour, the Yii heritage is an asset only if your team is already Yii people.

Editorial conclusion

Adopt Yupe if you are a PHP developer who already knows Yii Framework 1.x, you need a working shop skeleton quickly, and you are prepared to work in a codebase whose documentation is in Russian and whose core framework is a generation past its end of life. Do not adopt it as a starting point for a new long lived storefront if your team does not read Russian, and do not expect a modern PHP stack, since the stated minimum is PHP 7.0 with MySQL 5.x. Before you build, read install.md and the UPGRADE.md file in the repository, confirm the licence position for your use by reading the LICENSE file, and check the CHANGELOG.md to see how far the last release of 1.4 from 2021 has been maintained.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. yupe/yupe on GitHub