autotix/drupal-module

Drupal module that captures watchdog errors and forwards them to the Autotix webhook for automated Jira/GitHub ticket creation and auto-fix PRs.

v1.1.0 2026-07-22 18:06 UTC

Requires

• php: >=8.1
• drupal/key: ^1.18

Requires (Dev)

• autotix/php-sdk: ^0.2
• guzzlehttp/guzzle: ^7.0
• phpunit/phpunit: ^10.5 || ^11.0
• psr/log: ^3.0
• symfony/dependency-injection: ^5.4 || ^6.0 || ^7.0
• symfony/http-foundation: ^5.4 || ^6.0 || ^7.0

Suggests

• autotix/php-sdk: ^0.2 (bundled in lib/php-sdk/ as a fallback; composer-managed sites can require it and the bundled copy is ignored)
• drupal/core: ^10.3 || ^11.0 (declared via .info.yml core_version_requirement; only listed here for Composer-managed Drupal sites)

GPL-2.0-or-later

• Hello World Devs

Published on Packagist.org on 2026-07-22 18:08 UTC

README

Captures watchdog errors from your Drupal 10/11 site and forwards them to Autotix, which turns them into tickets (Jira or GitHub Issues) and AI-generated fix PRs automatically.

This repository is a read-only mirror, split from the Autotix monorepo. Issues and PRs are welcome here and will be applied upstream.

Requirements

• Drupal ^10.3 || ^11
• PHP >= 8.1
• Key module (secure credential storage)

Install

composer require autotix/drupal-module
drush en autotix

(The shared autotix/php-sdk core is bundled in lib/php-sdk/ as a fallback, so the module also works when copied into modules/custom without Composer.)

Configure

1. Create a Key (Administration → Configuration → System → Keys) holding your org webhook token from app.autotix.io → Settings.
2. Go to Administration → Configuration → Web services → Autotix (/admin/config/services/autotix).
3. Select the key, set your severity threshold and environment, and enable capture.

Settings include:

Setting	Default	Purpose
enabled	false	Master switch.
auth_method	token	token (X-Webhook-Token) or hmac (HMAC-SHA256).
severity_threshold	3 (Error)	Minimum RFC 5424 severity to forward.
dedup_window	86400	Seconds to suppress repeat sends of the same error.
send_immediately	false	Send inline instead of on destruct.
include_backtrace	false	Attach a formatted backtrace.

Testing the pipeline

Two options, from safest to most thorough:

1. Logged-error test (built in). Visit /admin/config/services/autotix/test to send a deliberate logged error end-to-end and confirm a ticket shows up in Autotix.

2. Fatal-error test (optional submodule). This module bundles a companion submodule, Autotix Test Error (autotix_error), that exercises the genuine uncaught-PHP-error path. Enable it, then visit /autotix-test-error (administrators only) to trigger a real fatal error:

   drush en autotix_error

   Leave it disabled in production — it only exists to verify capture.

Vulnerability Scanning

Alongside error capture, the module reports an environment fingerprint — Drupal/PHP versions plus resolved package versions — to Autotix, which matches it against advisory feeds and surfaces known-vulnerable dependencies. Reporting runs on hook_cron (once, then re-checked monthly and only re-sent when something changed); force an immediate report with:

drush autotix:report-env --force

The package list spans two ecosystems:

• Drupal modules (ecosystem: Drupal) — every installed module + version.
• npm packages (ecosystem: npm) — front-end JS dependencies with resolved versions read from package-lock.json (every lockfile format, direct + transitive). The module probes well-known locations without descending into node_modules: the Composer project root, the Drupal root, and custom theme/module/profile directories. A package.json with no committed lockfile is a best-effort fallback — only exact-pinned versions are reported, since a range is not a resolved install.

Development

composer install
vendor/bin/phpunit

The bundled SDK copy is kept in sync with the canonical source by bin/sync-sdk.sh and guarded by BundledSdkSyncTest.

License

GPL-2.0-or-later