Finds files and directories via an intuitive fluent interface
8.4k
Stars
55
Forks
0
Open issues
30
Contributors
AI Analysis
Symfony Finder is a component that locates files and directories using a fluent, intuitive API within PHP applications. It is best suited for developers building PHP applications or frameworks who need to programmatically search and filter file systems. This library benefits PHP developers and maintainers of larger applications but is not intended for end users or non-PHP contexts.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Symfony Finder: A mature PHP file-traversal component with 15+ years in production
symfony/finder is a standalone PHP component that provides a fluent, chainable API for locating files and directories on the filesystem — filtering by name, size, date, depth, content, and more. It was built for PHP developers who need more ergonomic control over filesystem traversal than raw SPL iterators offer. It is deeply embedded in the PHP ecosystem as a dependency of Composer, Symfony framework, Laravel tooling, PHPStan, and countless CLI tools. Its real-world adoption is among the highest of any PHP package.
Extracted from the Symfony framework around 2011 as a standalone component. It predates most modern PHP packaging conventions and has been continuously maintained through every PHP and Symfony major version since.
Star growth has effectively plateaued — not because interest declined, but because the component reached ubiquity years ago. It is pulled in as a transitive dependency by Composer, Symfony, and many other tools, meaning most users never consciously 'choose' it. Packagist download counts (not visible here) are in the billions, reflecting its silent omnipresence rather than viral adoption curves.
symfony/finder is a transitive dependency of Composer itself and of Symfony framework, Laravel's Illuminate packages, PHPStan, PHP-CS-Fixer, and many other foundational PHP tools. Packagist download statistics historically place it in the top handful of most-downloaded PHP packages globally, with billions of installs. Adoption is extensively verified at ecosystem scale.
Likely implements the Iterator/Composite pattern over PHP's SPL filesystem iterators. The fluent interface appears to wrap a chain of FilterIterators applied lazily. Based on the README, it supports filtering by name (glob/regex), path depth, file size, modification date, content (grep-style), and custom callables. Likely has no external runtime dependencies beyond the PHP standard library.
Not documented in README, but as a core Symfony component maintained since 2011 with contributions from hundreds of developers, comprehensive test coverage is highly probable based on Symfony's well-known testing culture.
Last push was 2026-06-05, approximately 3 weeks before the evaluation date. For a mature, stable utility component, this cadence is healthy — it is actively maintained without churn. Issues and PRs are handled in the monorepo at symfony/symfony.
ADOPT IF: you need structured, readable file traversal in any PHP project — this is the de facto standard and carries essentially zero risk. AVOID IF: you need cloud/remote filesystem abstraction; Finder is strictly local and that is by design. MONITOR IF: you are tracking whether the Symfony project's sponsorship appeal signals resource constraints that could affect long-term maintenance velocity.
Independent dimensions
Mainstream potential
3/10
Technical importance
7/10
Adoption evidence
9/10
- The README notes the package is 'looking for a backer', which may indicate financial pressure on Symfony's open-source maintenance budget, though this does not currently appear to affect release quality or cadence.
- As a local-filesystem-only tool, it provides no abstraction for remote or virtual filesystems — teams that later need cloud storage must integrate a separate layer.
- The forks count (55) is unusually low for a package this widely used, suggesting the community engages almost exclusively through the symfony/symfony monorepo — which may obscure the true contributor pool from a quick metadata scan.
- Deeply embedded transitive dependency status means breaking changes (however rare in Symfony's strict BC policy) can have wide downstream impact.
- No documented migration path for projects that outgrow local filesystem usage patterns — architectural replacement rather than upgrade would be required.
Will remain a permanent fixture of the PHP ecosystem for as long as server-side PHP exists. Likely to evolve incrementally with PHP version support rather than feature expansion.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://symfony.com/finder
- Language
- PHP
- License
- MIT
- Last updated
- 2w ago
- Created
- 187mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Top contributors
Similar repos
symfony/http-foundation
The HttpFoundation component provides an object-oriented abstraction layer for...
symfony/framework-bundle
FrameworkBundle is a core integration layer that binds Symfony components...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
symfony/finder
this
|
8.4k | — | PHP | 8/10 | 2w ago |
|
symfony/symfony
|
31.1k | — | PHP | 9/10 | 21h ago |
|
symfony/http-foundation
|
8.6k | — | PHP | 9/10 | 2w ago |
|
symfony/console
|
9.8k | — | PHP | 8/10 | 5d ago |
|
symfony/framework-bundle
|
3.6k | — | PHP | 9/10 | 2d ago |
|
symfony/symfony-docs
|
2.3k | — | PHP | 8/10 | 1d ago |
Flysystem abstracts filesystem storage across local, S3, FTP, etc. — a different problem. Finder is strictly for local filesystem traversal/discovery. They are complementary rather than competing.
Built-in PHP iterators are what Finder wraps and improves upon. SPL is more verbose and requires manual filter chaining. Finder is the ergonomic layer most developers prefer for non-trivial traversal.
PHP's native glob() and scandir() are simpler for basic use cases but lack composable filtering, depth control, and content matching. Finder covers the same simple cases and scales to complex ones.
Laravel-specific filesystem abstraction; focuses on read/write operations across drivers, not file discovery and filtering. Does not meaningfully compete with Finder's traversal API.
Narrower utility focused on glob pattern matching, including virtual filesystems. Finder is broader in scope; these can coexist in the same project.