PHPackages                             konafets/typo3-lib-installer - 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. konafets/typo3-lib-installer

ActiveComposer-plugin

konafets/typo3-lib-installer
============================

Composer plugin for installing PHP\_CodeSniffer standards

2.0.0(11y ago)08LGPL-3.0+PHP

Since Oct 21Pushed 11y ago1 watchersCompare

[ Source](https://github.com/Konafets/ComposerPlugins)[ Packagist](https://packagist.org/packages/konafets/typo3-lib-installer)[ RSS](/packages/konafets-typo3-lib-installer/feed)WikiDiscussions master Synced 2mo ago

READMEChangelogDependencies (2)Versions (8)Used By (0)

Composer Plugins
================

[](#composer-plugins)

A collection of composer plugins for specific installation instruction for composer packages.

PHP Codesniffer Standard installer
----------------------------------

[](#php-codesniffer-standard-installer)

The PHP Codesniffer Standard installer is able to install phpcs codesniffer standards into the `/squizlabs/php_codesniffer/CodeSniffer/Standards/`folder. By doing so the standard will be usable by calling `bin/phpcs --standard `.

### How To Use

[](#how-to-use)

- Find the package containing the codesniffs you want to use. This package should be a normal Codesniffing package containing a `ruleset.xml` and a `composer.json`.
- The composer package type has to be `phpcodesniffer-standard`
- The name of the package has to reflect the name of the standard (explained below)
- It's best if the package has a requirement to `simplyadmire/composer-plugins`. This is the only way to be sure the installer is available before the package is installed.
- Now add the package as a development dependency to your project
- Run `bin/phpcs -i` and see your standard listed

### Naming Rules

[](#naming-rules)

The name of the standard is derived from the composer packagekey. The part after the `/`is taken as standard name. The first character is made uppercase, and all characters after a `-` will be uppercased. So:

- `vendor/mysniffs` becomes `Mysniffs`
- `vendor/some-more-words` becomes `SomeMoreWords`

TYPO3 Specific
--------------

[](#typo3-specific)

The TYPO3 community already has packages available on packagist, and as renaming packagenames would be a bad practice we added 3 hardcoded standard names. Also the vendor name `TYPO3` will always be enforced to be uppercase.

To include the TYPO3 CGL to your project you can use one of the following commands (depending on the CGL you want to use, TYPO3 Flow or TYPO3 CMS):

TYPO3 Flow:

```
	composer require --dev typo3-ci/typo3flow=dev-master

```

TYPO3 CMS:

```
	composer require --dev typo3-ci/typo3cms=dev-master

```

Now you can sniff your packages with for example:

```
	bin/phpcs --extensions=php --standard=TYPO3Flow Packages/Application/My.Package

```

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity4

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity68

Established project with proven stability

 Bus Factor1

Top contributor holds 70% 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 ~123 days

Total

5

Last Release

4094d ago

Major Versions

1.0.3 → 2.0.02015-02-24

### Community

Maintainers

![](https://www.gravatar.com/avatar/b6aaf47df633cf9e260061e733e6cb82af4dabde0023bbcd2096dac330f41eb9?d=identicon)[Konafets](/maintainers/Konafets)

---

Top Contributors

[![radmiraal](https://avatars.githubusercontent.com/u/324613?v=4)](https://github.com/radmiraal "radmiraal (14 commits)")[![Konafets](https://avatars.githubusercontent.com/u/363363?v=4)](https://github.com/Konafets "Konafets (4 commits)")[![andygrunwald](https://avatars.githubusercontent.com/u/320064?v=4)](https://github.com/andygrunwald "andygrunwald (1 commits)")[![svemir](https://avatars.githubusercontent.com/u/154453?v=4)](https://github.com/svemir "svemir (1 commits)")

---

Tags

standardsphpcsPHP\_CodeSnifferTYPO3 CMStypo3TYPO3 FlowTYPO3 Neos

### Embed Badge

![Health badge](/badges/konafets-typo3-lib-installer/health.svg)

```
[![Health](https://phpackages.com/badges/konafets-typo3-lib-installer/health.svg)](https://phpackages.com/packages/konafets-typo3-lib-installer)
```

###  Alternatives

[dealerdirect/phpcodesniffer-composer-installer

PHP\_CodeSniffer Standards Composer Installer Plugin

596161.9M1.9k](/packages/dealerdirect-phpcodesniffer-composer-installer)[phpcompatibility/php-compatibility

A set of sniffs for PHP\_CodeSniffer that checks for PHP cross-version compatibility.

2.3k74.3M1.3k](/packages/phpcompatibility-php-compatibility)[phpcsstandards/phpcsextra

A collection of sniffs and standards for use with PHP\_CodeSniffer.

10224.3M44](/packages/phpcsstandards-phpcsextra)[phpcsstandards/phpcsutils

A suite of utility functions for use with PHP\_CodeSniffer

6233.4M58](/packages/phpcsstandards-phpcsutils)[phpcompatibility/phpcompatibility-wp

A ruleset for PHP\_CodeSniffer to check for PHP cross-version compatibility issues in projects, while accounting for polyfills provided by WordPress.

21830.6M587](/packages/phpcompatibility-phpcompatibility-wp)[drupal/coder

Coder is a library to review Drupal code.

3043.6M461](/packages/drupal-coder)

PHPackages © 2026

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