- Can I use jongotlin/ratsit-bundle in a Laravel application?
- No, not as shipped. It is a Symfony bundle built around a Bundle subclass, a DependencyInjection extension, and YAML configuration, and Laravel has no bundle concept or compiler passes. The realistic Laravel path is to use the underlying jongotlin/ratsit plain PHP client and wire it through a Laravel service provider and config file.
- How do I install Ratsit for Laravel with Composer?
- Do not require the Symfony bundle in a Laravel app. Require the underlying plain PHP Ratsit client if it is independently installable, then bind credentials and a PSR-18 HTTP client in a Laravel service provider. Keep vendor credentials in environment variables and config, not in version control.
- Does jongotlin/ratsit-bundle support Laravel 10, 11, or 12?
- It does not support Laravel 10, 11, or 12 as a bundle because it targets Symfony's bundle system. Laravel version support is not the deciding factor here; the framework-layer mismatch is. The plain PHP Ratsit client may work if it meets your PHP version and transport requirements, but that must be validated separately.
- What configuration and credentials does the Ratsit API need?
- The bundle exposes configurable API credentials through its Symfony configuration tree. In Laravel you would replicate that with config/ratsit.php and environment variables rather than YAML. Confirm the exact credential type, account requirements, and any per-environment settings directly with Ratsit.
- Does the Ratsit client support PSR-18 HTTP transport and PSR-3 logging?
- This is not established by the bundle overview and must be verified before adoption. If the client instantiates its own transport, you cannot cleanly apply your own retries, timeouts, circuit breaking, or log redaction. For a PII-bearing call path, lack of injectable PSR-18 and PSR-3 dependencies is a serious integration risk.
- What data can I look up with Ratsit for Swedish companies and individuals?
- The package advertises typed company and person lookup endpoints, with examples including address, age, and contact details. The exact response fields, data freshness, and lag versus official registries are not documented in the provided context. Validate the schema and freshness requirements against your use case before building on it.
- Is Ratsit GDPR compliant for Swedish personnummer lookups?
- The package does not answer GDPR compliance; it only wraps API calls. You still need a documented lawful basis, a DPA with Ratsit, Article 14 transparency handling, retention limits, and data-subject rights processes. Personnummer-based people search is sensitive and may carry higher risk depending on whether the purpose is onboarding, fraud review, or CRM enrichment.
- How much does the Ratsit API cost and what are its rate limits?
- Pricing, monthly minimums, rate limits, SLA, and API change notice periods are vendor terms from Ratsit, not properties of this bundle. The strategic dependency is Ratsit.se itself, not the small wrapper. Confirm commercial terms and deprecation policy directly with the vendor before committing.
- How do I test a Laravel integration with Ratsit without hitting the live API?
- Keep transport and domain logic separate, then inject a fake PSR-18 client or HTTP mock that returns recorded Ratsit fixtures. If the client instantiates its own transport internally, testing and failure simulation become much harder. Wrap the client behind your own interface so retries, timeouts, and error mapping can be tested in Laravel.
- Is jongotlin/ratsit-bundle maintained and safe for production?
- The available assessment shows zero stars, zero dependents, a single maintainer, pre-1.0 status, no SECURITY.md, and no CVE history in either direction. No known vulnerabilities is not the same as having been examined, and bus factor is one. For Laravel, use the plain PHP client behind your own provider or choose a vendor with documented REST and PSR-18 support; avoid installing the Symfony bundle.