The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Project link
https://www.drupal.org/project/sudc
Branch applying for
3.0.x (default branch)
Git clone command
git clone --branch 3.0.x https://git.drupalcode.org/project/sudc.git
Description
SearchUnify Drupal Connector integrates SearchUnify's AI-powered cognitive enterprise search platform with Drupal-powered websites. It unifies disparate content silos, fetches content, and displays contextually relevant search results ranked by relevance using NLP and machine learning algorithms. The module supports Drupal 10, 11, and 12.
How it differs from similar modules
Unlike standard Drupal search modules, this connector uses SearchUnify's generative AI, NLP, and machine learning engine to understand query context rather than just keywords. It provides intelligent autocomplete, personalized search results, and detailed analytics insights about user search behavior. It is the only Drupal module that directly integrates with the SearchUnify cognitive platform.
Release history
- 1.0.0 - February 6, 2024 (initial commit)
- 2.0.0 - October 21, 2024
- 2.0.4 - Drupal 12 support added
- 3.0.1 / 3.0.2 - latest stable releases (June 2025) — correct version + Drupal 12 support confirmed
Checklist
- README.md exists and follows official Drupal template
- Code is well commented following Drupal standards
- Branch naming follows Drupal conventions — 3.0.x is the default branch
- No LICENSE.txt file included (Drupal.org adds it automatically)
- No open security-tagged issues in the project queue
- Project is more than 10 days old (created February 6, 2024)
- GPL 2.0+ license applied
- Actively maintained with regular releases
- Latest release adds Drupal 12 support
Comments
Comment #2
neelam-webdev commentedComment #3
aman.kumar2Hi team,
I raised this issue 5 days ago and wanted to follow up. Is there any update on this issue?
Comment #4
aman.kumar2Hi,
just following up on the request for the SearchUnify Drupal Connector project on Drupal.org. Please let me know if you need any additional details from my side.
Comment #5
aman.kumar2Hi team,
I’m following up on this issue as I’ve already added several comments with the relevant details from my side. Please let me know if there are any updates or if anything else is needed from me to move this forward.
Comment #6
avpadernoComment #7
aman.kumar2Hi @avpaderno,
Thanks for the follow-up. I’ve reviewed the current implementation and confirmed that the 3.0.x branch is aligned with the latest stable release requirements, including Drupal 12 support. The remaining items in the checklist have been completed or verified, and I’m proceeding with final validation.
Please let me know if anything else is needed from your side, and I’ll update this issue accordingly.
Comment #8
avpadernoThe queue for being able to opt projects into security advisory coverage is the Drupal.org security advisory coverage applications one. Without creating an issue there, you will not get the permission to opt projects into security advisory coverage.
Comment #9
avpadernoSee #3577384: [1.0.x] Botshield, #3613219: [1.0.x] SDC Property Inheritance, or #3615077: [1.0.x] Instagram Feed Block, for example. None of the reviewers will review an application which was posted in a different queue.
Comment #10
aman.kumar2Hi @avpaderno,
As per the shared example, I have created a similar ticket and added the information to it. For your reference, please check and verify the ticket here:
https://www.drupal.org/project/projectapplications/issues/3615162
Comment #11
avpaderno