- Is ruudk/moneybird-bundle a Laravel package?
- No. ruudk/moneybird-bundle is a Symfony 2 bundle, not a Laravel package. It depends on Symfony's Bundle, DI Extension, and CompilerPass lifecycle, which Laravel does not implement. Composer may install it, but there is no Laravel service provider or facade integration.
- Can I use ruudk/moneybird-bundle in a Laravel application?
- Technically Composer can require it, but it will not work as a Laravel package. The bundle relies on Symfony kernel bundle registration and container wiring, so Laravel's service container will not load its services automatically. You would be fighting the framework to bridge Symfony 2 lifecycle code into a modern Laravel app. Treat it as incompatible rather than installable.
- What Moneybird API version does ruudk/moneybird-bundle target?
- It was last released in 2015, so it almost certainly targets Moneybird's legacy API rather than the current REST/JSON API with OAuth2. That likely means XML responses and per-user token or basic auth assumptions. You must validate the target version against the Moneybird developer changelog before any other analysis. If the version is retired, the package cannot be patched into working order because the protocol contract is gone.
- Is ruudk/moneybird-bundle still maintained?
- No. The repository is archived, the last release was 2015-08-04, and it has 3 stars and 0 dependents. Archived repositories are read-only, so there will be no upstream fixes, security advisories, or maintainer responses. No one else has validated its auth or error paths in the current ecosystem.
- Does ruudk/moneybird-bundle support PHP 8 and modern Laravel versions?
- No. The code is PHP 5.x-era and will hit reserved-word changes, removed mcrypt, dynamic property deprecations, and PSR/type mismatches on PHP 8.2+. Symfony 2.x is end-of-life with no security support. There is no declared support for modern Laravel versions.
- What does ruudk/moneybird-bundle actually include?
- It provides a Symfony DI extension, a configuration tree, and service definitions that wire a Moneybird API client into a Symfony 2 container. The HTTP transport, authentication, and DTO concerns are entangled with that container wiring. As a result, the useful code cannot be lifted cleanly into a framework-agnostic service layer.
- What should Laravel developers use instead of this bundle for Moneybird?
- Build a Laravel-native integration: a service provider that binds a typed Moneybird client, built on Saloon or a thin Guzzle wrapper with an OAuth2 grant, request and response DTOs, and retry/backoff middleware. Harvest only the bundle's domain vocabulary, such as contacts, invoices, sales invoices, ledger accounts, tax rates, payments, and webhooks, then discard the code. If a maintained community PHP SDK exists and passes security and activity review, prefer it over a custom client.
- Is there a migration path from ruudk/moneybird-bundle to a Laravel client?
- There is no real migration path because there is nothing worth migrating. Run a half-day to one-day spike that maps what the bundle assumes against current Moneybird API docs, then close the ticket if it targets a retired API version. A read-only reporting need is roughly a two-day build; bidirectional invoice sync is a program, not a migration.
- Is ruudk/moneybird-bundle safe to use in production?
- No. It is archived, unmaintained, has zero ecosystem signal, and likely targets a dead API version. No security advisories will be published, and its auth and error paths are unvalidated. Adopting it is effectively forking an unmaintained client with a misleading starting point, so do not consume it in production.
- How do I test a Moneybird integration in Laravel without this bundle?
- Do not test through this bundle; test the Laravel-native client you build instead. Use HTTP fakes or a mock handler with Saloon or Guzzle to assert request shape, OAuth headers, retries, and error mapping. Add a small number of contract tests against a Moneybird sandbox to catch API drift.