China Distpicker Laravel Package

Technical Evaluation

Architecture fit. laravel-admin-ext/china-distpicker is not a general-purpose Laravel package — it is a form-field extension for Encore's laravel-admin admin panel. It registers a distpicker field on the Form builder that renders a three-level cascading province → city → district selector, backed by a bundled static JS dataset. It introduces no service provider of consequence, no database schema, no API, and no server-side domain model. That makes it a UI concern only: it governs how an operator enters an address, not how the address is stored, validated, or used.

Integration feasibility. Binary and stack-dependent:

Technical risk. Ranked:

1. Dataset staleness (high). China's administrative divisions (统计用区划代码) are revised annually; county-level city → district conversions and new districts have been frequent since 2020. A 2021-10 release almost certainly predates several current divisions. Stale options mean operators pick wrong codes, which propagates into shipping and tax logic.
2. Upstream abandonment (high). No release in ~2.5 years, no visible PHP 8.2/8.3 CI, no CVE cadence. Because laravel-admin itself is in maintenance mode, this package sits on a decaying dependency chain — the highest-severity failure is being blocked from a Laravel upgrade by your admin panel.
3. Client-side-only enforcement (medium). The widget constrains input in the browser; nothing stops an invalid province/city/district combination from being POSTed or written by an API client. Server-side validation must be added by us.
4. Asset delivery posture (medium). If the JS is CDN-loaded rather than published to the app origin, that collides with CSP, offline admin environments, and data-residency review for China-hosted deployments.

Key questions for the maintainer (or our own fork):

• Which year of the national division codes does the bundled dataset reflect, and is there a regeneration script against an official source?
• Are assets vendored/published, or fetched at runtime?
• Is there a shipped Laravel validation rule for the three-column combination?
• Does it support fourth-level (street/township) or urban-rural classification, which logistics routing often needs?
• What is the license/provenance of the bundled distpicker JS and the division data (the wrapper is MIT; the data often is not)?