- Is scylabs/neptune-bundle a Laravel package?
- No. Despite some descriptions calling it a Laravel/PHP package, scylabs/neptune-bundle is a Symfony bundle, indicated by the -bundle suffix, ScyLabs namespace, and Symfony bundle conventions. It relies on the Symfony kernel, DI container compiler passes, bundle config trees, and Doctrine/Twig patterns, so it is not portable to Laravel. Treat it as a reference implementation at most if your target stack is Laravel.
- Can I install scylabs/neptune-bundle with Composer?
- It is Composer-installable in principle, but adoption is gated by license ambiguity, Symfony and Doctrine version constraints, and stale releases. Confirm its composer.json constraints against your Symfony LTS, PHP minor, Doctrine ORM, Twig, and mailer transport before installing. The last release was 2022-01-10, so expect PHPUnit and deprecation failures on modern PHP.
- Which Symfony versions does Neptune Bundle support?
- The bundle appears built for the Symfony 4.x/5.x and Doctrine ORM era, which is two major versions behind current Symfony. You must verify the exact composer.json constraints against your supported matrix for the next 18 months. Its pinned constraints may block framework upgrades, which is a worse risk than the feature it provides.
- What license is scylabs/neptune-bundle released under?
- The license is reported as NOASSERTION, meaning unknown rather than clearly permissive or copyleft. Legal cannot approve production use without written clarification from the maintainer, and this is a stop-ship issue for a commercial product. Resolve license clarity before any engineering spend.
- Is Neptune Bundle maintained and safe for production authentication?
- No. The last release was 2022-01-10, roughly three years without commits, with 2 stars, zero dependents, and a single maintainer. Because it covers registration, login, roles, password reset, and email confirmation, that means no CVE response path and concentrated, non-diversifiable risk. Do not adopt it without a funded fork-and-own commitment.
- What features does Neptune Bundle provide?
- It covers user and account management: registration, login, roles and permissions, profile editing, email confirmation, and password reset. It also centralizes configuration, registers required services, and exposes entry points for Neptune in Symfony. This is the highest-blast-radius auth domain, so it demands a higher maintenance bar than a utility library.
- How do I configure Neptune Bundle in a Symfony application?
- Configuration is via publishable config files and sensible defaults, with service container integration and standard bundle hooks. Confirm the exact config tree, required services, and adapter options from the bundle's README and config files before wiring it in. Because it targets older Symfony, test the config tree against your specific Symfony version.
- What are alternatives to Neptune Bundle for authentication?
- On Symfony, consider Symfony Security with MakerBundle or a maintained authentication bundle or package. On Laravel, use native auth options such as Breeze, Fortify, or Jetstream, and mine Neptune's entity and permission model only as design input. Compare license, maintenance activity, and version support before choosing.
- Can I use Neptune Bundle with an existing user table and auth flow?
- Greenfield only. Do not retrofit this into an existing user table or established auth flow, because schema, password hashing, and role model reconciliation is risky, and rollback in auth is not a safe operation. If you proceed, you own the schema from day one.
- Who maintains scylabs/neptune-bundle and what is the bus factor?
- A single maintainer with no visible contributor base, so the bus factor is one. There are 2 stars and zero dependents, meaning there is no community to inherit bug fixes from. If adopted, name an internally funded owner for the fork before writing any code.