zls/migration

Risky to adopt for a new project: the package has had no release or repository activity for over four years, and its linked repository does not clearly identify the package. It is not deprecated or archived, but maintenance and project ownership are difficult to verify.

Latest v1.2.6

Packagist

48%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 34 releases but none in the last 12 months, and its latest release was over four years ago. The established release history is a positive maturity signal, but the prolonged pause materially raises abandonment risk.

Repo commit activity

The repository recorded no commits and no active maintainers during the last three months, consistent with the package's long release gap. No newer activity is provided to offset this maintenance concern.

Package scaffolding

A README is present, but it is only 72 characters and directs users elsewhere for documentation, making the package harder to evaluate and use. The absence of tests and a changelog in the artifact is normal packaging practice and is not treated as a gap.

Repo package mention

The linked repository name does not match the package name and its README does not mention the package, so the repository may not clearly belong to this release. This weakens transparency about source and maintenance ownership.

Security policy

The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a hygiene concern, though it is less significant than the lack of recent maintenance.