xushilabs/xushiui

The package has a substantial component tree, an MIT declaration, no install-time scripts, and no deprecation or archive flag. Its identity documentation is inconsistent, and there is not yet enough release or commit history to establish dependable maintenance.

Latest v1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace is organization-like, but the linked repository is owned by an individual account, so the collected ownership data does not show organization backing that would compensate for a thin maintainer history.

Release history

This is the package's first release, published less than a day ago, so there is no track record of releases or maintenance yet. That is an early-maturity concern rather than evidence of abandonment.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Because the repository and package are brand new, this does not prove abandonment, but it leaves maintenance capacity unestablished.

Repo package mention

The repository name matches the package, but its README does not mention the package and instead presents the project as “Zayne UI.” That identity mismatch reduces transparency and may indicate copied or repurposed documentation.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tooling is present. The missing scanning is a modest transparency and maintenance gap.