- Is larping-base/larping-bundle a Laravel package or a Symfony bundle?
- It is published as a Symfony bundle, which is indicated by the -bundle suffix and the Symfony-style service and configuration wiring described in the blurb. There is no evidence in the overview of a Laravel ServiceProvider, Facade, or illuminate/support dependency, and the composer.json extra block is not confirmed to contain Laravel providers or aliases. Treat it as Symfony-shaped until you verify the source. For a Laravel application, that means you would need to write your own bridge or reimplement the integration.
- Can I install larping-base/larping-bundle in a Laravel 10, 11, or 12 application?
- Composer may allow the install if there are no hard framework constraints, but that does not make it Laravel-native. The package does not appear to declare illuminate/support constraints or Laravel auto-discovery, so you would be responsible for manually registering any services. Constraint conflicts against Laravel 10, 11, or 12 are likely and undocumented. The safer path is not to require it in a Laravel app at all.
- What license does larping-base/larping-bundle use?
- The license is reported as NOASSERTION, meaning it could not be machine-identified from the repository. That may indicate a missing LICENSE file, a modified license, or a bespoke license. Until your legal team reviews the actual repository contents and grants a written opinion, this package is a hard blocker for commercial or production use. Do not ship it before that clearance.
- What gateway does larping-base/larping-bundle actually connect to?
- The description only says it is a common gateway bundle for the larping application, which is too vague to identify the protocol, vendor, or endpoints. It could be an API gateway client, a payment abstraction, an SMS gateway, or an internal service entry point. Without that information you cannot assess the blast radius of adopting it. Review the source for hardcoded URLs, HTTP clients, and request signing logic before considering any use.
- Is larping-base/larping-bundle actively maintained?
- No. The package has one star, zero dependents, and its last release was in March 2024, leaving roughly two years without security patches. A bus factor of one with no evidence of an active maintainer means any bug you encounter becomes yours permanently. For an integration boundary that handles credentials and outbound HTTP, that maintenance profile is unacceptable for production.
- Does larping-base/larping-bundle have documentation or usage examples?
- There is no substantive README, no configuration reference, and no usage examples in the overview. Ramp-up cost is therefore read the source, which is a poor fit for a package that sits on an auth or gateway boundary. Undocumented timeout defaults, retry and backoff semantics, idempotency keys, and error taxonomy are exactly the behaviors that cause production incidents. You should assume you will own all of that knowledge yourself.
- How does larping-base/larping-bundle handle credentials and secrets?
- That is undocumented, and it is the most important thing to verify in the source before any spike. Check whether it logs request bodies or headers, whether secrets can be injected from environment variables or a vault, and whether it expects hardcoded configuration. An unaudited package handling credentials is a compliance concern, not just an engineering one. If you proceed at all, do so only after a security review of the HTTP layer.
- Does larping-base/larping-bundle have tests or a CI matrix?
- There is no evidence of tests, coverage, or a CI matrix proving supported PHP and framework versions. Gateway calls are the critical path, so you would want to see mocked HTTP tests plus at least one integration harness against a sandbox endpoint. Neither is documented. Do not assume test coverage exists because the package is on Packagist.
- What are the alternatives to larping-base/larping-bundle for Laravel?
- For Laravel, the realistic alternative is to fork or reimplement the small amount of code you actually need behind your own interface. Use Laravel's HTTP client, a maintained PSR-18 implementation such as guzzlehttp/guzzle, and your own ServiceProvider so the gateway dependency stays swappable and testable. That gives you a documented license, Laravel version constraints you control, and a real test suite. Adopting an unlicensed, stale Symfony bundle as a Composer dependency is not a viable alternative.
- Should I use larping-base/larping-bundle in production?
- No. It fails the minimum bar on legal clarity, provenance, maintenance, and documentation, with an unclear license, a single maintainer, zero dependents, and no release since March 2024. The recommended play is to treat it as a reference implementation to study, then fork or reimplement the parts you need. If you must reuse code, do it under a license your legal team has approved and with your own tests around every gateway call.