- Does manuelj555/upload-data-bundle work with Laravel?
- No, not as a drop-in dependency. The package is distributed as a Symfony bundle, and Laravel has no bundle system, so nothing will auto-register through package discovery. There is no evidence of a Laravel service provider, facade, or publishable config in the name, description, or metadata. Using it in a Laravel app would require a hand-written adapter or manual container wiring, which is more work than building the capability with native Laravel primitives.
- How do I install manuelj555/upload-data-bundle with Composer?
- You would install it with a standard composer require manuelj555/upload-data-bundle, but only after checking the composer.json constraints and the declared package type. In a Symfony app you would also register the bundle in config/bundles.php, which indicates it expects Symfony's kernel rather than Laravel's. In a Laravel project the install alone accomplishes nothing because there is no service provider to boot.
- Which PHP and Laravel versions does the package support?
- The last release was published on 2019-05-20, which puts it in the pre-PHP 8 era. That makes deprecation warnings and type-compatibility failures likely on modern PHP 8.2 and 8.3 runtimes. The package declares no illuminate/* dependencies, so Laravel version support is effectively undefined. Verify the declared PHP constraint and transitive dependency health with composer outdated and composer audit before assuming a clean install means compatibility.
- What license is manuelj555/upload-data-bundle released under?
- The license is not stated in the supplied package metadata, which is an OSS compliance blocker until verified. Check the repository for a LICENSE file and the composer.json license field before any commitment. A GPL-family license in particular would force a rip-out for most commercial Laravel codebases, so clear this with legal first. Do not treat a public GitHub repository as implicit permissive licensing.
- Is manuelj555/upload-data-bundle still maintained?
- The adoption and maintenance signals are weak: one star, zero dependents, and no release since May 2019. It has a single maintainer with no visible release cadence and no security policy, so there is effectively no upstream. That means you would own the code outright and absorb every future PHP and framework upgrade yourself. There is also no community CVE monitoring for the package.
- Does the bundle parse and import uploaded data, or only receive the file?
- The description mentions file processing and data extraction services, but nothing documents parsing, column mapping, or import workflow behavior in detail. Most packages in this category are thin wrappers around framework file transport plus validation. Before relying on it, confirm whether it actually parses and maps the contents or only accepts and stores the upload. If it only handles transport, native Laravel UploadedFile and Storage already cover that.
- Does it support large files, chunked uploads, malware scanning, or S3 object storage?
- There is no evidence in the metadata for any of these capabilities. Large-file handling, chunked uploads, MIME sniffing, malware-scan hooks, S3 object storage, multi-tenancy, and audit trails are all unverified. Given the 2019 release date, assume none of them are addressed until the source proves otherwise. These gaps usually decide the build-versus-adopt question on their own.
- What are the Laravel alternatives for upload and import workflows?
- Laravel's first-party primitives cover most of this: UploadedFile, Storage::putFileAs for transport, Form Requests for validation, and queued jobs for processing. For parsing, league/csv and maatwebsite/excel are maintained and widely used. For attachment lifecycle management, spatie/laravel-medialibrary is a stronger fit than an unmaintained Symfony bundle.
- How should I evaluate it before committing in a Laravel application?
- Run a timeboxed one-to-two day spike in an isolated branch: pin the commit, install it on your actual PHP and Laravel versions, and exercise the happy path. Alongside that, do a capability diff against your real requirements, separating transport from parsing from workflow. Put an application-level interface such as a DataFileIngestor in front of whatever implementation lands so it stays replaceable. Clear the license before any of this work begins.
- Can I use manuelj555/upload-data-bundle as a reference implementation instead of a dependency?
- Yes, and that is the recommended approach given the high technical risk and low integration payoff. Read the bundle for concepts around upload handling and data extraction, then reimplement them on UploadedFile, Storage, Form Request validation, and queued processing. A small, well-tested in-house module will be cheaper than an adapter, a pinned fork, and ongoing compatibility tests. If you do adopt any code, vendor the fork under your own namespace and pin the commit.