Technical Evaluation

Architecture fit: fortephp/sheath-statamic appears to be a Statamic-focused addon for Sheath, providing diagnostics for Antlers templates. It fits the Laravel/Statamic stack as a development-time tool rather than a production runtime dependency. For a TPM, the value is shifting template syntax and region issues left into local development and CI.
Integration feasibility: Feasible via Composer as a dev dependency, with Statamic addon enablement and CI/local execution. The v0.1.1 patch specifically fixes false Antlers region syntax diagnostics, which improves signal quality and reduces developer noise. However, public integration details are thin; confirm exact commands, configuration, and output formats before committing.
Technical risk: Low production risk if kept dev-only. Medium adoption risk due to v0.1.x maturity, likely single-maintainer ownership, and dependence on Antlers parser behavior. The v0.1.1 fix is a positive maintenance signal but also confirms that diagnostic false positives are a real operational concern. No breaking changes are indicated in this patch.
Key questions: Is the package strictly dev-only? Which Statamic and PHP versions are supported? How are diagnostics surfaced—CLI, editor/LSP, PHPStan extension, or Statamic addon UI? Can it fail CI on errors? How configurable are rules and suppressions? What is the license, security posture, and maintainer roadmap? Does it require the Sheath core package?

Integration Approach

Stack fit: Best suited as a Composer require-dev package in Laravel/Statamic repositories. It complements existing PHPStan/Pint/CI checks by covering Antlers template diagnostics, especially region syntax. It should not be introduced as a production dependency.
Migration path: No data or runtime migration. Add the package, enable the Statamic addon if required, run in advisory mode against a representative template set, baseline existing diagnostics, then promote to CI checks for changed templates. Updating from v0.1.0 to v0.1.1 is a patch-level Composer update with no stated breaking changes.
Compatibility: Validate against the team’s Statamic major version, PHP version, and Antlers feature usage. Test region-heavy templates specifically, since that is the v0.1.1 fix area. Confirm no conflicts with existing template linters or Statamic addons.
Sequencing: 1) Spike in one non-critical Statamic project; 2) measure false positive/negative rate after v0.1.1; 3) add as non-blocking CI advisory; 4) document suppression workflow; 5) make blocking only for new or modified templates; 6) expand to additional sites after stability is proven.

Maintenance: Low if dev-only and version-pinned. Review releases quarterly and track maintainer activity. The single-maintainer risk should have an internal contingency plan, such as falling back to manual template review or removing the check if the package stalls.
Support: Expect community/GitHub-based support rather than vendor SLA. Assign an internal owner to triage false positives, manage suppressions, and communicate diagnostic expectations to developers.
Scaling: Scales per repository/CI job rather than per production request. Large Antlers template sets may increase lint time; monitor CI duration and consider scoping checks to changed files. Centralize configuration across multiple Statamic sites where possible.
Failure modes: False diagnostics blocking CI, parser incompatibility after Statamic/Antlers upgrades, package abandonment, PHP version conflicts, and unclear suppression paths. Mitigate with advisory-mode rollout, version pinning, baseline files, and a documented escape hatch.
Ramp-up: Low for Statamic developers; moderate for teams new to Sheath. v0.1.1’s region diagnostic fix reduces onboarding friction, but teams still need guidance on interpreting diagnostics, suppressing false positives, and using the tool consistently in CI.