- What is pierre-arthur/sf-doctor?
- It is a diagnostic and audit CLI for Symfony projects, described as running health checks across configuration and integrations. It is a Symfony-ecosystem tool rather than a Laravel package. The available metadata does not detail the exact checks it performs or how findings are scored.
- Can I use sf-doctor in a Laravel application?
- Probably not directly. Laravel uses Symfony components, but the tool is described as auditing Symfony project structure, bundles, and container conventions that Laravel apps do not follow. A composer require into a Laravel app is unlikely to produce useful output without adaptation. Its better role for Laravel teams is as a reference design for a first-party health-audit command.
- How do I install sf-doctor?
- The expected path is Composer: add the package and invoke its console command. The supplied data does not confirm the exact package name constraints, command name, or install steps. Verify the README and Packagist metadata before adding it to a project.
- Which PHP and Symfony versions does sf-doctor support?
- The provided evaluation does not list supported PHP or Symfony versions. Build a version matrix of your runtimes against the package's declared Composer constraints before piloting. If it only supports the newest Symfony major, older services are out of scope immediately.
- Does sf-doctor modify my project files or dependencies?
- That is not confirmed in the supplied information. An audit tool should be read-only, but the evaluation explicitly flags this as something to verify. Check the source before running it in a project where writes would be a risk.
- Does sf-doctor output JSON for CI gating?
- The output format is unverified. The evaluation asks whether it emits machine-readable JSON or only human-readable console text. Until confirmed, treat it as a report-only tool in CI rather than a build-blocking gate.
- Is sf-doctor safe for production use?
- Adoption signals are weak: roughly 11 stars, zero dependents, and a single author. You would likely be among the first real consumers and would absorb undiscovered edge cases. Run it in report-only mode on a low-criticality project before trusting it more broadly.
- Is sf-doctor actively maintained?
- The metadata lists a last release date of 2026-05-01, which the evaluation flags as anomalous and worth reconciling against Packagist tags and the changelog. There is no evidence of a co-maintainer or governance, and license and stability are also unverified. Confirm release history before relying on it.
- How does sf-doctor compare to PHPStan, Psalm, or Rector?
- It is complementary rather than a replacement. Those tools do static analysis and automated refactoring, while sf-doctor is described as a project hygiene and configuration audit. It is redundant only if your existing tooling already covers that audit gap.
- Should Laravel teams adopt sf-doctor or build their own doctor command?
- For a Laravel-centric team, mining sf-doctor for requirements is usually the higher-leverage path. Use its rule set and report structure as a spec for a php artisan doctor command you control. Adopt the package directly only if you actually run Symfony services.