PHPackages                             sbuerk/typo3-cms-styleguide-version-sync - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. sbuerk/typo3-cms-styleguide-version-sync

ActiveMetapackage[Utility & Helpers](/categories/utility)

sbuerk/typo3-cms-styleguide-version-sync
========================================

Meta package to require correct typo3/cms-styleguide version for used TYPO3 version

13.4.2(1y ago)046GPL-2.0-or-later

Since Dec 15Pushed 1y ago1 watchersCompare

[ Source](https://github.com/sbuerk/sbuerk-typo3-cms-styleguide-version-sync)[ Packagist](https://packagist.org/packages/sbuerk/typo3-cms-styleguide-version-sync)[ RSS](/packages/sbuerk-typo3-cms-styleguide-version-sync/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (10)Dependencies (2)Versions (38)Used By (0)

Meta Package - sbuerk/typo3-cms-styleguide-version-sync
=======================================================

[](#meta-package---sbuerktypo3-cms-styleguide-version-sync)

Background
----------

[](#background)

The `typo3/cms-styleguide` extension does not require any TYPO3 system extension and multi version usage in a project or extension with multi core support requirements have a hard time to manage the correct styleguide version for the actual used TYPO3 version.

This meta package does only provide version releases containing only the require for one specific styleguide version and `typo3/cms-core` to finally allowing to simply require multiple version and let composer detect and use the correct on.

Usage
-----

[](#usage)

**simple-case / autodetection**

```
composer require "sbuerk/typo3-cms-styleguide-version-sync"
```

**advanced / version seletion**

Repository tagging and releases will be aligned with the `typo3/cms-styleguide` versions and when required with the concrete core version required for it as minimum.

For example, if styleguide 11 and 12 is required and you want to ensure that 11 is used with TYPO3 v11.5.x and 12 with TYPO3 v12.4.x you would use following command to add it to your project or extension:

```
composer require "sbuerk/typo3-cms-styleguide-version-sync":"^11 || ^12"
```

You could also more concrete version:

```
composer require "sbuerk/typo3-cms-styleguide-version-sync":"^11 || ^12.0.5"
```

Versions
--------

[](#versions)

[Github Releases](https://github.com/sbuerk/typo3-cms-styleguide-version-sync/releases) lists all available versions, read each release notes to get information for that specific release version.

Note metapackage starts with TYPO3 v11 + TYPO3 Styleguide v11, earlier releases are not covered by this metapackage.

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance40

Moderate activity, may be stable

Popularity8

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity50

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

37

Last Release

513d ago

Major Versions

11.x-dev → 12.0.02024-12-15

12.x-dev → 13.0.02024-12-15

### Community

Maintainers

![](https://www.gravatar.com/avatar/22ea8c0796de498c0d81554f12539e71bdb9b9359df3a82a7fb450867a68a680?d=identicon)[sbuerk](/maintainers/sbuerk)

---

Top Contributors

[![sbuerk](https://avatars.githubusercontent.com/u/1453466?v=4)](https://github.com/sbuerk "sbuerk (38 commits)")

### Embed Badge

![Health badge](/badges/sbuerk-typo3-cms-styleguide-version-sync/health.svg)

```
[![Health](https://phpackages.com/badges/sbuerk-typo3-cms-styleguide-version-sync/health.svg)](https://phpackages.com/packages/sbuerk-typo3-cms-styleguide-version-sync)
```

###  Alternatives

[eliashaeussler/typo3-form-consent

Extension for TYPO3 CMS that adds double opt-in functionality to EXT:form

1481.0k](/packages/eliashaeussler-typo3-form-consent)[b13/assetcollector

Add CSS and SVG files and strings as inline style tag/inline svg to the html code.

10118.4k](/packages/b13-assetcollector)[mfd/ai-filemetadata

Automatically generates FAL metadata for files by means of public LLMs

1142.1k](/packages/mfd-ai-filemetadata)[mautic/mautic-typo3

Add-on TYPO3 extension that enhances the "EXT:marketing\_automation" TYPO3 extension by connecting it to the Mautic Marketing Automation platform: Determine "Persona" from Mautic segments. Also provides additional services e.g. language synchronisation between Mautic and TYPO3.

236.3k](/packages/mautic-mautic-typo3)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)