teamtnt

teamtnt/laravel-scout-tntsearch-driver

PHP MIT Web Dev

Driver for Laravel Scout search package based on https://github.com/teamtnt/tntsearch

1.1k stars
141 forks
recent
GitHub

1.1k

Stars

141

Forks

17

Open issues

30

Contributors

v15.0.0 18 Feb 2025

AI Analysis

A Laravel Scout driver that integrates TNTSearch, a full-text search library, enabling developers to add local, file-based search to Laravel models without external services. Best suited for Laravel applications that need search functionality but prefer to avoid managed search platforms like Elasticsearch or Algolia; particularly valuable for smaller teams, self-hosted projects, and applications with moderate search requirements.

Web Dev Library Discovery value: 5/10
Documentation 7/10
Activity 8/10
Community 8/10
Code quality 5/10

Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.

Overall score 7/10

AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.

laravel-integration search-engine full-text-search scout-driver php-package
Actively maintained MIT licensed Niche/specialized use case Production ready
Deep Analysis · Based on README and public signals
5d ago

Specialized full-text search driver for Laravel Scout, offering local-file-based indexing as Elasticsearch alternative

laravel-scout-tntsearch-driver is a PHP package that integrates TNTSearch, a pure-PHP full-text search engine, into Laravel Scout (the framework's official search abstraction layer). It enables developers to add search functionality to Laravel models without external infrastructure dependencies. Adoption appears concentrated among Laravel developers seeking search without managing Elasticsearch or similar services. The project maintains steady adoption via Packagist but shows no evidence of rapid growth or shifts in use patterns.

Origin

Created in August 2016, the driver emerged to complement the TNTSearch engine (sibling project, 3200 stars) as a Scout integration layer. Scout itself launched in Laravel 5.3, creating immediate demand for pluggable search drivers. The driver has evolved to support Laravel versions 5.3 through 12, tracking framework releases closely.

Growth

Star count stabilized around 1,100–1,136 over available observation window; zero net stars gained in last 7 days indicates mature-phase adoption rather than emerging traction. Package downloads via Packagist (exact figures unavailable in metadata) likely represent the true adoption signal. The 141 forks suggest fork-and-customize patterns typical of niche infrastructure packages. No evidence of inflection points or viral adoption phases.

In production

Adoption not verified in README or metadata. No case studies, user testimonials, or production deployment examples provided. Packagist download statistics (not visible in metadata) would be the primary adoption signal, but counts unavailable. Open Collective backers/sponsors mentioned, indicating some financial support, but scale unknown. Presence of a premium analytics product (noted in README) suggests parent organization (TeamTNT) maintains broader commercial interest in the ecosystem.

Code analysis
Architecture

Based on README, the driver acts as a Scout driver adapter, delegating search operations to TNTSearch (a separate library). Appears to manage model indexing, constraint-based filtering, and query execution through Laravel Scout's standardized interface. Likely uses file-based index storage in the storage/ directory rather than a remote service. Model-level configuration via `toSearchableArray()` method follows Laravel Scout conventions.

Tests

Not documented in README. Travis CI badge is present but URL appears outdated (travis-ci.org); CI status unavailable in metadata.

Maintenance

Last push 2026-06-16 (19 days before analysis date) indicates active maintenance. Supports Laravel 12 (current major version as of mid-2026), suggesting tracking of framework releases. However, absence of changelog, recent issue counts, or PR activity in metadata limits ability to assess maintenance intensity. Slow-but-steady pattern (not stagnant) based on version support currency.

Honest verdict

ADOPT IF: you require full-text search in a Laravel project, operate at small-to-medium scale (<500k records), prefer self-hosted and zero-infrastructure solutions, and your queries are not performance-critical. AVOID IF: you operate at high query volume, require advanced relevance tuning, need cloud-hosted managed search, or must support complex Boolean/faceted queries reliably. MONITOR IF: you are evaluating Scout drivers and want to verify real-world production usage; adoption claims lack public evidence but maintenance is active.

Independent dimensions

Mainstream potential

3/10

Technical importance

5/10

Adoption evidence

3/10

Risks
  • Adoption not independently verified; real-world production usage at scale is undocumented—risk of unforeseen limitations only discovered after deployment.
  • File-based indexing may encounter concurrency issues or scalability constraints at high write frequency or large dataset sizes; no README mention of locking mechanisms or performance boundaries.
  • Test coverage and CI/CD status not transparent (Travis CI badge URL outdated); reduces confidence in backward compatibility and regression prevention across Laravel version upgrades.
  • Parent organization (TeamTNT) promotes premium analytics product in README, creating potential concern about prioritization of open-source maintenance vs. commercial product roadmap.
  • TNTSearch engine itself (parent library) is a pure-PHP implementation; query performance may lag specialized search engines (Elasticsearch, Meilisearch) at scale, but README does not document performance benchmarks or acceptable dataset/query rate thresholds.
Prediction

Project will likely remain a stable, slow-growth niche tool for small-to-medium Laravel projects prioritizing operational simplicity over search performance. Unlikely to displace managed search services in mainstream adoption, but may solidify as the de facto Scout driver for budget-constrained or infrastructure-minimal deployments. Risk of gradual decline if Laravel Scout itself loses adoption or if cloud search becomes default assumption.

0 found this helpful

Newsletter

Get analyses like this every Monday

Free weekly digest of the most interesting open-source discoveries.

Languages

PHP
100%

Information

Language
PHP
License
MIT
Last updated
3w ago
Created
121mo ago
Analyzed with
anthropic/claude-haiku-4-5

Stars over time

Loading…

Contributors over time

Top 100 contributors only — repos with more will plateau at 100.

Loading…

Similar repos

teamtnt

teamtnt/tntsearch

TNTSearch is a full-text search engine written entirely in PHP that enables...

3.2k PHP Dev Tools
laravel

laravel/scout

Laravel Scout is a driver-based full-text search abstraction layer for...

1.7k PHP Web Dev
spatie

spatie/laravel-searchable

Laravel Searchable is a Laravel package that enables structured search across...

1.4k PHP Web Dev
protonemedia

protonemedia/laravel-cross-eloquent-search

This Laravel package enables searching across multiple Eloquent models...

1.1k PHP Web Dev
artesaos

artesaos/seotools

SEOTools is a Laravel and Lumen package providing helpers for common SEO...

3.4k PHP Web Dev
vs. alternatives
Laravel Scout (native Elasticsearch/Meilisearch drivers)

Scout's native drivers require external services; TNTSearch driver offers self-hosted, file-based indexing with no infrastructure overhead—trade-off favors simplicity over scale and performance at query volume.

Spatie Laravel-Searchable

Spatie's package (1375 stars) uses database queries directly rather than a separate search index, simpler but slower for full-text matching on large result sets.

Meilisearch Scout driver

Meilisearch (via Scout) provides cloud-hosted or self-hosted search with superior performance and relevance tuning; TNTSearch trades feature depth for minimal operations overhead.

TNTSearch (parent library, 3200 stars)

This driver is a wrapper around TNTSearch; parent library can be used directly outside Laravel Scout for non-Laravel PHP projects, but Scout integration handles model binding and command integration.

Protonemedia Laravel-Cross-Eloquent-Search

Cross-Eloquent-Search uses database-backed full-text search, avoiding external indexing; lower latency but less suitable for complex text relevance scenarios.