Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Currency Bundle

Currency Bundle Laravel Package

flagbit/currency-bundle

Flagbit CurrencyBundle is a PHP/Symfony bundle for handling currencies and exchange rates. It provides services for currency conversion, formatting, and managing currency data, helping applications display and calculate monetary values reliably across multiple currencies.

View on GitHub
Deep Wiki
Context7

FlagbitCurrencyBundle for the Symfony Framework

Frequently asked questions about Currency Bundle
Can I use flagbit/currency-bundle in Laravel?
No. FlagbitCurrencyBundle is a Symfony FrameworkBundle: it registers through AppKernel, uses DependencyInjection Extension and Configuration classes, and wires services with compiler passes. Laravel has no bundle registry, Extension/Configuration contract, or compiler-pass lifecycle, so the package installs but nothing executes. Only the PSR-11 container boundary overlaps, which is not enough to make it usable in a Laravel app.
Does flagbit/currency-bundle support Laravel 10 or 11?
There is no Laravel support at all, for 10, 11, or any version. The bundle targets the Symfony 2/3 era and PHP 5.x/7.x, so Composer will likely fail dependency resolution against Laravel 10/11, which run Symfony 6/7 and PHP 8.1+. Expect composer require to fail on resolution rather than install and misbehave.
Is flagbit/currency-bundle maintained?
No. The repository is archived, with 0 stars, 0 dependents, and a scanner score of 0.05. Archived means no security response, no PHP-version compatibility work, and no upstream fixes. Any CVE in a transitive dependency becomes permanently yours.
How do I install flagbit/currency-bundle?
You would normally add it via Composer, but installation in a Laravel project is not meaningful because the bundle's code is never bootstrapped. In a Symfony app of the right vintage you would register the bundle in AppKernel and configure it through the Extension. For Laravel, do not install it; treat the source as a reference spec instead.
What alternatives to flagbit/currency-bundle should I use in Laravel?
Use a framework-agnostic money library such as moneyphp/money or brick/money for value objects and arithmetic, paired with a Laravel-native service provider for configuration and bindings. For exchange rates, call an active FX provider through a small, tested client you own. These cover currency storage, conversion, and formatting without Symfony wiring.
How do I do currency conversion and formatting in Laravel?
Represent amounts with a money value object such as moneyphp/money or brick/money rather than floats, and store minor units as integers plus a currency code. Wrap rate lookup and conversion in a service bound as a singleton in a Laravel service provider, configured via config/currency.php. Format for display with a formatter class or NumberFormatter, keeping presentation out of the domain.
Does flagbit/currency-bundle store exchange rates as floats?
The overview does not specify, and this is a discovery question you must answer by reading the source. Float storage for monetary values is a correctness defect you would inherit, so check the rate and amount column types. If they are floats, do not adopt the logic as-is.
How much work is it to port a Symfony bundle to Laravel?
It is a rewrite, not a configuration exercise: Extension becomes a ServiceProvider, the config tree becomes config/currency.php, service definitions become container bindings, and Symfony event subscribers become Laravel listeners. The effort is only justified if the domain logic, meaning the currency entity, rate retrieval, and conversion arithmetic, is non-trivial and cleanly separable from Symfony wiring. For a bundle of this vintage, that cannot be assumed.
Is flagbit/currency-bundle safe to use in production?
No. It is archived with no production evidence such as stars or dependents, and adopting it would make you the first adopter of a package nobody has run in anger. The high technical risk is concentrated in the dependency graph, where a transitive CVE would be permanently yours. Reject it for direct adoption and retain it only as a reference implementation.
What is flagbit/currency-bundle's license and can I vendor its code?
It is BSD-3-Clause, which is permissive and low-friction, requiring attribution only. If you vendor or derive code from it, confirm the attribution and license notice are retained. The license is not a blocker; the stack fit and maintenance status are.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core