Download the PHP package cru/fluidlint without Composer
On this page you can find all versions of the php package cru/fluidlint. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download cru/fluidlint
More information about cru/fluidlint
Files in cru/fluidlint
Package fluidlint
Short Description Linting, cyclomatic complexity and dead-code analysis for TYPO3 Fluid templates
License GPL-3.0-or-later
Homepage https://github.com/Rathch/fluidlint
FAQ
Example:
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 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.
Informations about the package fluidlint
fluidlint
Static analysis for TYPO3 Fluid templates: structural issues, cyclomatic complexity, and dead-code hints — without bootstrapping TYPO3.
SPDX-FileCopyrightText: 2025 Christian Rath-Ulrich
SPDX-License-Identifier: GPL-3.0-or-later
fluidlint scans Fluid templates directly from the filesystem. PHP ViewHelper classes are not analyzed (use PHPStan/PHPCS for that). On TYPO3 14.2+, complement this tool with typo3 fluid:analyze for syntax errors, invalid ViewHelpers, and deprecations.
Requirements
- PHP 8.2+
typo3fluid/fluid2.15+ (TYPO3 v13) or 4.x (TYPO3 v14)
Installation
In your TYPO3 project or extension as a dev dependency:
Quick start
Commands and options
| Command | Description |
|---|---|
scan |
All checks (structure, complexity, dead code) |
complexity |
Cyclomatic complexity per template |
dead-code |
Unreachable branches, unused variables, orphan partials |
Common options:
| Option | Description |
|---|---|
--format=text\|json\|sarif |
stdout output format (default: text) |
--fail-on=info\|warning\|error |
Minimum severity for exit code 1 |
--config=FILE |
Path to .fluidlint.yaml (default: project root) |
--exclude=PATTERN |
Exclude glob pattern (repeatable) |
--report-file=FILE |
Write detailed JSON report to file |
-v / --verbose |
Confirm report file path after writing |
Paths in CLI output and reports are relative to the scan start path (the first directory argument, or .).
Configuration
Create .fluidlint.yaml in your project root. Defaults ship in config/fluidlint.defaults.yaml.
Thresholds
- nestingDepth — maximum ViewHelper nesting depth
- complexity — cyclomatic complexity (
f:if,f:for,f:switch, …) - failOn — minimum severity that causes exit code 1
Dead-code settings
- entryPoints — templates from which references are considered reachable
- orphanSeverity — severity for unreferenced partials/layouts (
info,warning,error) - excludeOrphanPatterns / excludeAnalysisPatterns — exclude paths from orphan or dead-code analysis (e.g.
**/Resources/Extensions/**)
Individual rules can be enabled or disabled under rules::
Detailed report
In addition to stdout output, a separate JSON report can be written with all findings and per-file complexity calculations. The stdout format (--format) is independent — the report is always JSON.
Via CLI:
Via configuration:
--report-file overrides report.path. Missing parent directories are created automatically. File paths in the report are relative to the scan start path.
The report contains:
| Field | Description |
|---|---|
generatedAt |
Analysis timestamp |
filesScanned |
Number of templates scanned |
issueCount |
Number of findings |
thresholds |
Active threshold settings |
complexity |
Per-file complexity including calculation breakdown |
issues |
All findings with context |
Per file under complexity:
| Field | Description |
|---|---|
complexity |
Total score (base 1 plus branching ViewHelpers) |
branchCounts |
Points per ViewHelper (e.g. f:if: 3) |
contributions |
Individual contributions with line and points |
Checks
| Category | Rules |
|---|---|
| Structure | fluid/parse-error, fluid/nesting-depth, fluid/empty-section, fluid/duplicate-section |
| Complexity | complexity/threshold-exceeded |
| Dead code | dead-code/unreachable-then, dead-code/unreachable-else, dead-code/unreachable-case, dead-code/unused-variable, dead-code/unused-partial-argument, dead-code/partial-all-arguments, dead-code/orphan-partial, dead-code/orphan-layout, dead-code/unused-section |
TYPO3 projects
Standalone CLI (recommended for most projects):
TYPO3 extension (console command inside TYPO3):
Both use the same analysis engine.
CI example
Archive the JSON report as a CI artifact or feed it into dashboards.
Limitations
- Conditions depending on runtime controller variables cannot be classified as dead code
- Dynamic partials (
f:render partial="{name}") are not resolved - Action templates without Extbase mapping may be reported as orphans (usually
info) - TypoScript with unresolved constants (
{$...}) is ignored f:renderwith_allskips per-argument checks
License
GNU General Public License v3.0 or later — see LICENSE.
All versions of fluidlint with dependencies
typo3fluid/fluid Version ^2.15|^4.0
symfony/console Version ^6.4|^7.0
symfony/finder Version ^6.4|^7.0
symfony/yaml Version ^6.4|^7.0