Laravel Genderize Api Client Laravel Package

Product Decisions This Supports

• Feature delivery: A Laravel-native client for the Genderize.io first-name gender inference API — useful for form autofill/pre-fill, personalized greetings and copy, audience segmentation in analytics, and lightweight demographic enrichment of signup or CRM data.
• Platform roadmap: v13.0.0 is primarily a support-window release. It tells you the package will track Laravel majors 1:1 (package major = highest supported Laravel major), so Laravel 12/13 upgrade planning can include this dependency without a bespoke compatibility review each cycle.
• Build vs. buy: The package is a thin wrapper (config, facade, Laravel service-provider conventions) around one HTTP API. If you already have a hardened HTTP client layer and observability, building the ~100 lines in-house is viable; buying this is justified mainly by convention-fit and low maintenance overhead, not by unique capability.
• Security/compliance decision: The framework constraint now excludes Laravel versions affected by the published CRLF injection and temporary signed URL advisories. That is a forcing function: adoption of v13 also forces an application-level framework patch, which is a security-hygiene win you can cite in review.
• Risk decision: Gender inference is probabilistic and processes a personal-data attribute (first name → inferred gender). Decide deliberately whether it belongs in anything user-visible or decision-adjacent (pricing, eligibility, hiring, ad targeting). Recommended scope: cosmetic/personalization and aggregate analytics only — not eligibility, profiling, or sensitive-category inference.
• Deprecation cleanup: The facade alias fix (Woocommerce → Genderize) removes a confusing leftover; teams that worked around discovery with a manual alias should schedule removal, which is a small but real migration task to slot into the sprint.

When to Consider This Package

Adopt when:

• You are on Laravel 12.61.1+ or 13.x and PHP 8.3, 8.4, or 8.5 — anything older cannot install v13.
• You want a zero-friction, idiomatic integration (service provider, facade, config publish) rather than hand-rolling an HTTP client and retry logic.
• Your use case is presentational or aggregate (greetings, defaults, segmentation), where a probabilistic signal is acceptable.
• You accept a fast-major cadence: expect a new package major roughly every Laravel major, and a corresponding drop of the oldest supported Laravel/PHP pair. Pin with ^13.0 and plan an annual dependency-review slot.

Look elsewhere / defer when:

• You are still on Laravel 10.x or 11.x or PHP 8.1/8.2. You are capped at v12.0.0, which is deprecated and receives no further releases — treat that as a hard migration deadline, not a stable resting place.
• You cannot send first names to a third-party API (data residency, GDPR/DPA constraints, minors' data). Consider a self-hosted or provider-agnostic inference path instead.
• You need gender inference as a decision input rather than a cosmetic signal; the accuracy and fairness profile of name-based inference is not defensible for consequential decisions.
• You require vendor-neutral abstraction across multiple enrichment providers — this package is single-provider by design.
• You need offline/batch-at-scale processing with caching and rate-limit orchestration beyond what a thin wrapper provides.

Migration notes to plan for: require ^13.0, ensure Laravel ≥ 12.61.1 on PHP ≥ 8.3, and drop any manual Woocommerce alias registration — Genderize is auto-registered.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a small, low-risk Laravel integration for a name-to-gender inference API, used for personalization and analytics enrichment — not for any decision affecting a user's access, price, or eligibility. The new v13.0.0 release adds no new product capability; its value is that it keeps us on supported, security-patched versions of Laravel. Adopting it requires our application to be on Laravel 12.61.1+ and PHP 8.3+, which also closes out two published framework security advisories. The cost is a routine dependency bump plus a small cleanup of a misnamed alias; the risk is low and the alternative — staying on the deprecated v12 line — is the riskier path.

For engineering (the short version):

• Package major now mirrors Laravel major (^13.0 = Laravel 13.x and 12.x). Simple, predictable rule; put it in the dependency policy.
• Breaking: drops Laravel 10/11 and PHP 8.1/8.2. Composer will refuse the old framework versions anyway due to security advisories, so this is aligned with reality rather than a surprise.
• Breaking (minor but real): facade alias corrected from Woocommerce to Genderize. Remove manual alias registrations; update any Woocommerce:: references.
• Toolchain moved to PHPUnit ^12.5.8 (12.5 schema), PHPStan on PHP 8.3, and a test matrix spanning Laravel 12/13 × PHP 8.3/8.4/8.5 — a good signal that CI actually covers the supported surface.
• Supply-chain hygiene improved: workflow actions pinned to commit SHAs and changelog automation uses an admin token when configured.

Recommendation: Approve the upgrade as part of the current Laravel/PHP maintenance window, with the caveat that any product use of gender inference stays presentational and is reviewed against our data-processing obligations before launch.