Download the PHP package conduction/coding-standard without Composer

On this page you can find all versions of the php package conduction/coding-standard. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package coding-standard

conduction/coding-standard

PHP CS Fixer configuration for Conduction's Nextcloud apps. It extends nextcloud/coding-standard and adds rules to it — never overrides them.

The rule this package enforces

Conduction code must pass Nextcloud's own coding standard unchanged. We may be stricter than Nextcloud. We may not be different from it.

That is enforced by construction, not by review. Conduction\CodingStandard\Config extends Nextcloud's and merges a private ADDITIONS array on top of parent::getRules(). tests/invariants.php fails the build if ADDITIONS shares a single key with the parent set, so a Nextcloud rule cannot be redefined even by accident.

The suite also asserts that no parent rule is dropped, that no parent rule's value changed, and that the indent is a literal tab — and each of those has a positive control proving the assertion can fail. A suite that cannot fail is indistinguishable from one that passes.

Why it exists

Measured 2026-08-12 against openregister's lib/: all 1,427 files failed nextcloud/coding-standard. curly_braces_position 100%, indentation_type 98.7%, phpdoc_align 85.6%, binary_operator_spaces 77.4%, cast_spaces 47.4%, concat_space 40.9%.

The fleet had been formatting PHP with a PEAR-derived PHP_CodeSniffer ruleset — four spaces, next-line braces, (int) $x, 'a'.'b' — under script names (cs:check / cs:fix) that belong to nextcloud/coding-standard, which 17 of 18 apps also carried in require-dev without ever invoking it. That was not a stricter standard; it was a different dialect wearing the right label.

Usage

The require_once is not optional. .php-cs-fixer.dist.php is included by php-cs-fixer before your autoloader runs, so without it the file dies with Class "Conduction\CodingStandard\Config" not found — and in --format=json mode that fatal is reported as zero files needing changes, which reads exactly like a clean tree.

What ADDITIONS contains, and why it is empty

Empty is a result, not an omission.

Every rule this fleet wants beyond Nextcloud's is semantic, not typographic — named parameters on internal calls, an @spec tag on public API, no \OC::$server, no var_dump / die / error_log. php-cs-fixer cannot express any of them. They live in PHP_CodeSniffer, which the fleet now runs for semantics only, with every whitespace, brace and alignment sniff removed precisely so the two tools cannot contradict each other.

On formatting, we want exactly what Nextcloud wants.

Adding a key here is therefore a real decision. It must be a rule Nextcloud has no opinion on; the test refuses it otherwise.

Division of labour

Concern Tool Config
Formatting — whitespace, braces, imports, quotes, casts php-cs-fixer this package
Semantics — named parameters, @spec, banned functions, removed NC APIs, line length PHP_CodeSniffer quality-config/ in ConductionNL/.github
Types Psalm + PHPStan quality-config/

The PHPCS ruleset carries a test asserting it reports zero findings on php-cs-fixer-formatted fixtures. That is the automated form of the measurement that produced this split, and it is what stops the two tools drifting back into conflict.

Registry

Published on Packagist as conduction/coding-standard, so composer require --dev conduction/coding-standard needs no repositories block. That matters beyond convenience: a per-app repositories entry is a per-app file, and per-app files are what drift.

Tags reach Packagist through the push webhook Packagist installs on submission — https://packagist.org/api/github, push events. Nothing to configure by hand, but do check a real delivery after the first tag: a hook that exists and 403s looks identical to one that works, and a ping succeeding proves only that the endpoint answers a handshake.

Further reading


All versions of coding-standard with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
nextcloud/coding-standard Version ^1.4
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package conduction/coding-standard contains the following files

Loading the files please wait ...