slimphp/Slim · PHP
Micro-framework for PHP. Small, focused codebase.
Source:
slimphp/Slim· commite12cb05· scanned 2026-05-23
Analyze slimphp/Slim (PHP) at commit e12cb05 for technical debt. Summarize severity distribution, top rules triggered, and SQALE rating.
Scanned 79 issues in 100ms.
At a glance
| Issues | SQALE rating | Remediation | Scan time |
|---|---|---|---|
| 79 | A | 6d 11h | 100ms |
Severity distribution
| critical | high | medium | low |
|---|---|---|---|
| 0 | 19 | 58 | 2 |
Top rules triggered
| Rule | Severity | Count |
|---|---|---|
nesting-depth | high | 72 |
file-length | high | 5 |
todo-comment | low | 2 |
Raw scan data: slim.json
What kind of debt is this? Show the SQALE breakdown by category.
Remediation time by debt category — where the work would land if you fixed everything:
| Category | Remediation |
|---|---|
| maintainability | 19d 2h |
| code-quality | 1h |
The bulk of remediation lives in maintainability — that's where a debt-reduction sprint would have the highest ROI.
Show me the worst issues — top high-severity findings with file paths.
Top 5 high-severity findings:
| Severity | Rule | Location |
|---|---|---|
| high | nesting-depth | Slim/CallableResolver.php:142 |
| high | nesting-depth | Slim/Exception/HttpTooManyRequestsException.php:28 |
| high | nesting-depth | Slim/Factory/AppFactory.php:144 |
| high | nesting-depth | Slim/Handlers/ErrorHandler.php:188 |
| high | nesting-depth | Slim/Middleware/BodyParsingMiddleware.php:164 |
What dependencies does it use?
# Dependency Analysis
**Project:** td-showcase-slimphp-Slim-e12cb05ca2a1-1779575569272
**Found:** 1 package file(s) across 1 ecosystem(s)
**Total Dependencies:** 25
**Ecosystems:** composer
## composer.json (composer)
**Dependencies:** 25
### Production (9)
- php@~7.4.0 || ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0
- ext-json@*
- nikic/fast-route@^1.3
- psr/container@^1.0 || ^2.0
- psr/http-factory@^1.1
- psr/http-message@^1.1 || ^2.0
- psr/http-server-handler@^1.0
- psr/http-server-middleware@^1.0
- psr/log@^1.1 || ^2.0 || ^3.0
### Development (16)
- ext-simplexml@*
- adriansuter/php-autoload-override@^1.4 || ^2
- guzzlehttp/psr7@^2.6
- httpsoft/http-message@^1.1
- httpsoft/http-server-request@^1.1
- laminas/laminas-diactoros@^2.17 || ^3
- nyholm/psr7@^1.8
- nyholm/psr7-server@^1.1
- phpspec/prophecy@^1.19
- phpspec/prophecy-phpunit@^2.1
- phpstan/phpstan@^1 || ^2
- phpunit/phpunit@^9.6 || ^10 || ^11 || ^12
- slim/http@^1.3
- slim/psr7@^1.6
- squizlabs/php_codesniffer@^3.10
- vimeo/psalm@^5 || ^6What should I fix first?
Dedicate Time for Tech Debt Reduction — 19 high-severity issues found. Consider allocating sprint time for tech debt.
Improve Code Maintainability — Several files have maintainability issues like deep nesting or excessive length.
How do I reproduce this locally?
Clone the repo at the pinned commit:
git clone https://github.com/slimphp/Slim.git
cd Slim && git checkout e12cb05ca2a14e8f459d019e87a31dc915b80470Option 1 — npx (any MCP client)
Add to your client's MCP config:
{
"mcpServers": {
"tech-debt": { "command": "npx", "args": ["-y", "tech-debt-mcp@latest"] }
}
}Then call analyze_project with the absolute path to the clone.
Option 2 — Claude Code plugin
/plugin marketplace add PierreJanineh/TechDebtMCP
/plugin install tech-debt-mcp@techdebtmcpThen ask Claude Code: "Run analyze_project on this directory."
Spot a false positive?
Open an issue with the showcase-fp label and link this page. Existing reports for slimphp/Slim.
Tech Debt MCP is a static analyzer. It identifies patterns that often indicate debt — not all flagged code is broken, and not all debt will be flagged. Repository authors are not responsible for these findings.