- Is imanaging-document/check-format-bundle compatible with Laravel?
- Not directly. By its -bundle suffix and description it follows Symfony Bundle conventions, so it has no Laravel service provider, no config publish step, and no package auto-discovery. You would need to adapt or fork the underlying logic rather than install it as a normal Laravel package.
- How do I install check-format-bundle in a Laravel application?
- There is no standard Laravel install path. Composer may resolve the package, but registration assumes a Symfony kernel and bundles.php rather than Laravel's provider model. Inspect composer.json and the source before adding it to require, because Symfony framework constraints can conflict with Laravel's own symfony/* pins.
- What exactly does check-format-bundle validate in a document?
- The public description only says it checks file format, which is too thin to know whether it uses extension allow-listing, MIME sniffing, magic-byte inspection, or structural validation. You must read the code to confirm. That distinction matters because upload-gating checks need magic-byte inspection and fail-closed behavior, not extension-only logic.
- Is check-format-bundle safe for validating uploads in production?
- Treat it as high risk until audited. It has had no release since June 2022, no visible test evidence, and no published issue history, so its handling of malformed or adversarial files is unknown. Do not rely on it as a security boundary for document uploads without verifying its validation method and failure behavior.
- Which Laravel and PHP versions does check-format-bundle support?
- The context does not state supported Laravel or PHP versions, and as a Symfony bundle it most likely declares Symfony component constraints instead. Those constraints can conflict with the symfony/* versions Laravel already ships. Check composer.json and run it on your target PHP 8.2 or 8.3 branch to catch deprecations.
- Why is check-format-bundle a Symfony bundle instead of a Laravel package?
- The -bundle suffix and the phrasing in its description are Symfony Bundle conventions. A Symfony bundle registers through bundles.php or the Kernel and does not use Laravel's ServiceProvider or auto-discovery mechanisms. The domain logic may still be framework-agnostic, but the packaging is not Laravel-native.
- Is imanaging-document/check-format-bundle still maintained?
- There is no release since 2022-06-24, only one star, and zero dependents. That means you would become the maintainer on day one if you adopt it. For a small validation utility, forking or reimplementing is usually cheaper than depending on a dormant package.
- Does check-format-bundle have a test suite or CI pipeline?
- There is no CI badge or other evidence of a test suite in the available information. Coverage of malformed, ambiguous, or adversarial inputs is therefore unknown. If you fork it, add tests around format detection and failure modes before trusting it in a document workflow.
- What should I use instead of check-format-bundle in Laravel?
- For most Laravel apps, use Laravel's validation rules such as mimes and mimetypes, backed by explicit magic-byte checks through fileinfo where security matters. You can also consume Symfony MIME or Finder components directly, since Laravel already ships several Symfony components. Reimplementing the thin format-check layer as a custom rule is often the cleanest path.
- Can I fork check-format-bundle and reuse its logic in Laravel?
- Yes, the MIT license permits forking and redistribution. The functional scope appears small, likely a few hundred lines, so extracting framework-free classes into a Laravel validation rule and config or filesystem mapping is feasible. First confirm whether the core logic depends on Symfony's DI container, Kernel, or HttpFoundation.