Paweł Górski

> audit --drupal-risk

Drupal audit

I review a Drupal project that works but carries risk: custom code, updates, integrations, performance and areas that can block the next release.

  • A list of real risks and their project impact
  • Repair priorities: now, later, watchlist
  • A recommended next step without a heavy process

When to order it

When the project needs assessment before a deadline, budget or handover decision

01

Inherited code

I separate ordinary technical debt from issues that can realistically cause failure or delay.

02

Uncertain release

I check what must be repaired before deployment and what can safely wait.

03

Low trust in changes

I organize risks in custom code, integrations and updates so the team has a clear plan.