Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Coding Standards Laravel Package

typo3/coding-standards

TYPO3 Coding Standards provides shared PHP_CodeSniffer rules and tooling to enforce consistent, TYPO3-specific PHP coding conventions. Integrate with CI and local development to automatically detect style issues, improve code quality, and keep contributions uniform.

Deep Wiki
Context7

Technical Evaluation

Architecture fit: The package is a PHP_CodeSniffer ruleset specifically designed for TYPO3 projects, fitting seamlessly into standard PHP-based TYPO3 development stacks. It extends PHPCS functionality without requiring additional infrastructure, making it ideal for TYPO3 extension and application development where code consistency is critical.

Integration feasibility: High. As a Composer dependency, installation is straightforward (composer require typo3/coding-standards). Integration into CI/CD pipelines (e.g., GitHub Actions, GitLab CI) requires minimal configuration to run phpcs against codebases. PHPCS is widely adopted in PHP ecosystems, ensuring compatibility with existing tooling.

Technical risk: Moderate. The repository's unknown status and moderate stars (66) indicate limited community validation. Potential risks include version-specific compatibility issues with TYPO3 (e.g., LTS versions 11.x/12.x) or PHP (e.g., 8.1+), and possible conflicts with custom PHPCS configurations. The MIT license reduces legal risk, but lack of clear maintenance history could lead to outdated rules.

Key questions: What TYPO3 and PHP versions are explicitly supported? How does the package handle custom extension-specific conventions? Are there known issues with PHPCS 4.x or newer PHP versions? What is the update frequency and process for addressing breaking changes in TYPO3?

Integration Approach

Stack fit: Perfect for TYPO3-centric projects using Composer and PHPCS. Aligns with standard TYPO3 extension development workflows and modern PHP practices, including PSR-12 compliance with TYPO3-specific enhancements. Works alongside existing tools like PHP-CS-Fixer or IDE integrations.

Migration path: For new projects: Add via Composer, configure phpcs.xml to reference the ruleset, and run initial checks. For existing projects: Replace current PHPCS ruleset with this package, run local fixes (phpcbf), then enforce via CI. Requires updating CI config to include vendor/bin/phpcs commands.

Compatibility: Likely compatible with TYPO3 LTS versions (11.x, 12.x) and PHP 7.4+. Must verify PHPCS version requirements (e.g., PHPCS 3.7+). Should coexist with other linting tools if configured properly (e.g., using separate rulesets for different tooling).

Sequencing: 1) Install package via Composer; 2) Generate phpcs.xml with

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
davejamesmiller/laravel-breadcrumbs
artisanry/parsedown
bower-asset/punycode
bower-asset/inputmask
bower-asset/jquery
bower-asset/yii2-pjax
laravel/nova
spatie/laravel-mailcoach
spatie/laravel-superseeder
laravel/liferaft
nst/json-test-suite
danielmiessler/sec-lists
jackalope/jackalope-transport
twbs/bootstrap4
php-http/client-implementation
phpcr/phpcr-implementation
cucumber/gherkin-monorepo
haydenpierce/class-finder
psr/simple-cache-implementation
uri-template/tests