Weave Code
Utilities Bundle Laravel Package
kunstmaan/utilities-bundle
A small Symfony utility bundle from Kunstmaan providing shared helper classes for slug generation, string and class manipulation, and common file/URL tasks. Useful across Kunstmaan bundles and handy for everyday backend work in Symfony projects.
Kunstmaan Utilities Bundle is a lightweight PHP package that collects reusable helpers and utility classes shared across the Kunstmaan ecosystem. It saves you from reimplementing common plumbing — string manipulation, array handling, and small framework-agnostic services — so you can drop it into a project and focus on application logic instead.
- Reusable helpers for strings, arrays, and general data handling
- Framework-friendly integration with minimal configuration
- Composer-ready installation and autoloading
- Battle-tested across Kunstmaan's own bundle suite
- MIT-licensed and easy to extend
Frequently asked questions about Utilities Bundle
- Can I install kunstmaan/utilities-bundle in a Laravel application?
- No, not in any practical sense. The package is a Symfony bundle that ships a Bundle class, a DI extension, and Symfony 2.x-era service definitions, and Laravel has no bundle or DI-extension concept to wire those into. Its require block will also collide with the Symfony 6/7 components that Laravel 10 and 11 ship, so Composer platform checks typically fail before you get anywhere.
- Does kunstmaan/utilities-bundle support Laravel 10, Laravel 11, or PHP 8?
- It supports none of them. The last release was 2014-06-16, there have been no commits in roughly a decade, and there is no PHP 7.2+ or 8.x support. The cipher service almost certainly depends on mcrypt, which was removed in PHP 7.2, so the package cannot run on any currently supported PHP runtime without a rewrite.
- What does the Kunstmaan UtilitiesBundle actually contain?
- Despite the broad name, the functional surface is very small: a symmetric string cipher service and an OS process (shell) helper. Everything else in the package is the Symfony integration layer that makes those two classes available through the container. Only the two service classes contain portable logic; the wiring is not reusable outside Symfony.
- What should I use instead of this bundle for encrypting strings in Laravel?
- Use the framework's built-in encryption: Crypt::encryptString() and Crypt::decryptString(), or the Illuminate\Encryption\Encrypter class directly. Laravel's encrypter uses AES-256-CBC with an HMAC authentication tag, and supports AES-256-GCM if you configure it, so you get authenticated encryption and key handling for free. That replaces the bundle's cipher entirely with a maintained, first-party primitive.
- Is kunstmaan/utilities-bundle secure to use in production?
- No. Rijndael 256 as implemented in that era typically means AES-256 in ECB or CBC with a static or derived key and no authentication tag, which is not a compliant primitive for PII, PCI, or GDPR-scoped data under current expectations. The shell helper is also a risk surface: kill-by-PID with weak ownership checks can terminate unrelated processes on shared hosts, PID-only liveness checks are vulnerable to PID reuse, and any parameter reaching exec or shell_exec is a command-injection vector.
- How do I migrate data that was already encrypted with this bundle?
- Only that interoperability requirement justifies touching the original code at all. Write a one-time decrypt-and-re-encrypt migration that reads the legacy ciphertext with openssl_decrypt using the original key and mode, then stores it again via Crypt::encryptString(), and retire the old path once the backfill is verified. Keep the legacy key available only for the duration of that migration, then rotate it.
- What replaces the shell and background process helper in Laravel?
- Use symfony/process, which is already a transitive Laravel dependency, or the Process facade for short-lived command execution. For long-running or background work, move the job onto a queue with Horizon, SQS, or Redis rather than managing subprocesses and PIDs yourself. That removes the PID-reuse and kill-by-PID failure modes entirely.
- Is kunstmaan/utilities-bundle actively maintained?
- No. The repository is a read-only subtree split of the KunstmaanBundlesCMS monorepo, the last release was 2014-06-16, and there is no security response capability or maintainer actively fixing issues. It has around 12 stars, 0 dependents, and a composite score of 0.24, so there is no production evidence base and no third party to inherit fixes from.
- Can I extract just the utility classes into my Laravel project instead of installing the package?
- Yes, and that is the only realistic path. Treat the repository as a specification document rather than a dependency: reimplement the two behaviours as small internal services behind interfaces you control. Estimated effort for idiomatic equivalents with tests is on the order of a few days, versus an open-ended port-and-maintain obligation, so name an owner and a deprecation date for anything you copy.
- How do I test a Laravel replacement for this bundle's cipher and shell helper?
- Feature-test the cipher by asserting round trips through Crypt::encryptString() and decryptString(), plus a migration test that decrypts a known legacy ciphertext fixture and re-encrypts it. For the process helper, use Process::fake() or inject a process runner interface so tests never spawn real subprocesses. Also pin the app key handling in config and assert that a wrong or rotated key fails loudly rather than silently returning garbage.
Weaver
How can I help you explore Laravel packages today?