- What is outofoffice/password-generator used for?
- It is a Laravel Nova form field that adds a random password generation control to Nova resource forms. Although its package name and blurb suggest a general-purpose generator, the shipped repository is nova-password-generator and the artifact is a Nova field backed by a Vue component. It is intended for admin-side credential creation, not as a standalone password library.
- Is outofoffice/password-generator a standalone Laravel password generator or a Nova field?
- The name and description point in different directions, but the repository and shipped code are a Laravel Nova field. The broader standalone-library description is not supported by the code you install. Treat it as a Nova-only package until you read the source and confirm otherwise. This distinction changes integration effort significantly.
- How do I install outofoffice/password-generator?
- Run composer require outofoffice/password-generator, then reference the field class in a Nova resource's fields() method. The package renders a compiled Vue asset, so there is no backend service or schema change. Most of the install is normal Nova field registration, but Nova asset compilation and version compatibility should be tested in staging.
- Which Laravel Nova versions does outofoffice/password-generator support?
- The last release is v1.8.1 from February 2023, which predates Nova 5 by about ten months. Check the package's composer.json for its Nova constraint and test it against your actual Nova, Laravel, PHP, and Node/Vite versions. Do not assume Nova 5 compatibility from the README; verify it with a spike in staging.
- How do I set password length and character options?
- The field is described as configurable for length and character sets, typically through fluent methods on the field instance in your resource. The exact method names and defaults should be confirmed from the source or README before relying on them. Also check whether there is a minimum length or character-set floor, since that affects security posture.
- Does it use a cryptographically secure random generator?
- This is unverified and is the most important security question. Because the field is a Vue component, generation is likely client-side; if it uses Math.random() instead of window.crypto.getRandomValues(), the output is unsuitable for security-relevant credentials. Audit the randomness source before using it for real accounts.
- Does fillOnCreate populate both password and confirmation fields?
- The v1.8.1 release was a typo fix for fillOnCreate(), which is the behavior you would depend on for auto-filling on create. Whether it fills both the password and confirmation inputs is not established in the provided context. Verify this in a Nova form; otherwise you may generate mismatched-password support tickets.
- Is outofoffice/password-generator maintained?
- No meaningful maintenance is visible: the last release was in February 2023, the repository has about 11 stars, zero dependents, and no visible CI or active maintainer. Adopting it means owning a fork. MIT licensing makes that legally easy, but you still need to review and maintain the code.
- Can I use outofoffice/password-generator outside Laravel Nova?
- Based on the shipped repository, no. It is a Nova form field with a Vue component, not a general Laravel or plain PHP password generator. For non-Nova Laravel apps, use Laravel's Str::password() or a maintained CSPRNG library instead. The wider blurb should not be treated as evidence of a standalone API.
- What are alternatives to outofoffice/password-generator for Laravel?
- For Nova forms, a plain password field plus server-side generation with Laravel's Str::password() or random_bytes() is simpler and avoids an unmaintained dependency. For a standalone generator, use a maintained library with a documented CSPRNG and clear character-set rules. If you need the Nova UI control specifically, fork this package under your own namespace and verify Nova compatibility.