Skip to main content

Review: New Drupal Contrib Code Search Tool Indexes Drupal 10+ Compatible Projects

· 3 min read
Victor Jimenez
Victor Jimenez
Software Engineer & AI Agent Builder

A new public code search service now targets Drupal contrib projects compatible with Drupal 10+, with a UI at search.drupal-api.dev and an API at api.tresbien.tech. For maintainers and upgrade teams, this is immediately useful: you can query real contrib code patterns before writing migrations, patches, or architecture decisions.

What Is Actually New​

From Theodore Banta's launch write-up, this is not a tiny index. The service reports:

  • 68,000+ Drupal contrib repositories indexed.
  • 6,900+ PHPStan baseline files indexed.
  • Support for filtering by project metadata (for example, core compatibility and package type).

If those numbers stay current, this is one of the most practical "signal over noise" additions to Drupal contrib research in 2026.

What I Verified Directly​

I verified these endpoints with live requests:

  • GET /v1/search?q=... returns code matches and file/repository context.
  • GET /v1/search/repo returns repository metadata from the index.

Example:

curl -s "https://api.tresbien.tech/v1/search?q=hook_help&num=2"

That returns a structured JSON payload with Result metadata plus matching files, which makes it usable for tooling, not just manual browsing.

Why This Matters for Drupal 10/11 and Drupal CMS​

For current Drupal work, the main value is workflow speed:

  • Deprecation hunts: search for patterns you need to replace across compatible contrib code.
  • Implementation discovery: find real module examples instead of relying on stale snippets.
  • Risk triage: inspect how maintainers are handling API shifts before you choose your own migration path.

I infer Drupal CMS usefulness from Drupal 10/11 compatibility and contrib focus. The source announcement does not claim a separate Drupal CMS certification tier.

Caveats​

  • The service quality depends on index freshness and coverage quality over time.
  • API and docs are still early-stage; endpoint docs and behavior should be validated in your pipeline before hard coupling.
  • Treat it as a high-leverage research input, not a substitute for module-level review and tests.

Bottom Line​

This is a strong addition to the Drupal engineering toolbox. If you maintain contrib integrations or run Drupal 10/11 upgrades, the new search index can cut research time and improve decision quality, especially when combined with your own static analysis and CI checks.

Why this matters for Drupal and WordPress​

Drupal maintainers running upgrade sprints from Drupal 9 to 10/11 can use this search index to find real-world deprecation handling patterns across thousands of contrib modules instead of guessing at migration approaches. For agencies managing both Drupal and WordPress properties, the ability to search contrib code for integration patterns (REST, JSON:API, authentication hooks) accelerates cross-CMS architecture decisions. WordPress developers familiar with the Plugin Directory code search will recognize the value of having an equivalent index on the Drupal side.

References​

Looking for an Architect who doesn't just write code, but builds the AI systems that multiply your team's output? View my enterprise CMS case studies at victorjimenezdev.github.io or connect with me on LinkedIn.