- What is joshluongo/laravel-aus used for?
- It is a Laravel utility package that bundles common Australian data validators and formatters. According to its description, it covers ABNs, ACNs, TFNs, Medicare numbers, postcodes, states and territories, phone numbers, and currency. It ships ready-made validation rules and helper functions so you do not have to hand-roll Australian-specific checks in each application. It is aimed at Australian-facing apps that need compliant input validation and consistent output formatting.
- How do I install joshluongo/laravel-aus in a Laravel app?
- Install it through Composer using the package name joshluongo/laravel-aus, which is the standard path for Laravel packages of this shape. The package's own overview is minimal, so check the repository README and composer.json for the exact install command, minimum PHP version, and any post-install steps. Pin an exact version rather than a caret range while you evaluate it. Install on a feature branch first and run your application test suite before merging.
- Which Laravel and PHP versions does this package support?
- The supplied package documentation does not state a Laravel or PHP version floor, so treat compatibility as unverified until you check. Look at the require block in the package's composer.json and any CI matrix in the repository to see which Laravel majors and PHP versions are actually tested. Then validate the constraint graph against your application lockfile with a dry-run Composer update. A transitive dependency conflict is the most common failure point for packages like this.
- How do I validate an Australian ABN in Laravel?
- The package ships ready-made validation rules, so ABN validation is intended to be used the same way as any built-in Laravel rule, such as in a form request or a validator call. The exact rule class name or string alias is not included in the supplied documentation, so confirm it in the README or package source before wiring it into your rules array. Validate against a handful of known-good and known-bad ABNs in a test to confirm behaviour before relying on it in production. If you also need to accept formatted input, check whether the rule or a helper normalises spaces before checking the checksum.
- Does laravel-aus validate ACN, TFN and Medicare numbers?
- Yes. The package description explicitly lists ACNs, TFNs and Medicare numbers alongside ABNs as supported validators. These identifiers each use their own checksum logic, which is one of the main reasons to use a dedicated package rather than a generic regex. Confirm the exact rule names in the README and add explicit tests for each type you rely on. Keep in mind that Medicare numbers are sensitive personal data, so handle and log them accordingly.
- Can laravel-aus format Australian phone numbers and currency?
- The package describes both phone number and currency handling as part of its feature set, alongside the validators. Formatting helpers are typically used to present stored values consistently, for example turning raw digits into a local or international phone format, or rendering amounts as AUD. The precise helper signatures are not in the supplied documentation, so check the package source for method names and return types. Test edge cases such as mobile versus landline prefixes and negative or zero currency amounts before depending on the output.
- Does laravel-aus handle Australian postcodes, states and territories?
- Yes, postcodes, states and territories are both listed in the package description. That usually means a validation rule that checks a postcode falls in a valid Australian range and a rule or helper that restricts a value to the known state and territory codes. Whether the postcode rule only checks ranges or also maps postcodes to states is not stated, so verify in the source if that mapping matters to you. Do not assume cross-field validation between postcode and state exists unless you confirm it.
- Do I need to register the service provider or publish a config file for laravel-aus?
- Most Composer-distributed Laravel packages of this kind rely on package auto-discovery, in which case no manual provider registration is needed. The supplied documentation does not confirm whether this package ships a config file, facade, or migrations, so check the repository before installing. If your application disables auto-discovery, you will need to add the provider to the providers array in config/app.php manually. Review any published config file and diff it against the package default rather than copying it blindly.
- Is laravel-aus safe to use in production, and does it make network calls?
- The supplied material does not document outbound network calls, telemetry, or implicit route and middleware registration, so verify these by reading the service provider and any middleware in the source. For a validation and formatting package, there is normally no reason to transmit data off-host, and you should treat anything that does as a blocker under most data-handling policies. Because release notes for v1.2.0 were empty, there is no changelog signal to lean on. Run a staging deployment with production-shaped data behind a feature flag and keep a rollback path before going live.
- Is laravel-aus still maintained, and what changed in v1.2.0?
- The package appears to be a single-maintainer project with a low bus factor, which is a real risk for anything in a revenue path. The v1.2.0 release notes supplied were empty, so there is no changelog, deprecation, or breaking-change signal available for that version. Before adopting it, check the commit history, issue response times, open-to-closed issue ratio, and whether it ships its own test suite and CI matrix. If you need stronger guarantees, compare against actively maintained alternatives or vendor a small internal validator for the identifiers you actually use.