solital/katrina

Usable with caveats: it has a stable release, tests, a changelog, and a matching source repository, but there has been no release or commit activity for about two years. Very low adoption and no security policy or scanning add maintenance risk.

Latest 2.6.4

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the release history, this indicates maintenance has effectively paused for about two years.

Project backing

The registry namespace and repository owner are both solital, and the owner is a user account rather than an organization. This provides consistent ownership but limited organizational backing.

Release history

The package has 29 releases since June 2020, but none in the last 12 months and its latest release was about two years ago. The long historical cadence is positive, while the current inactivity is a meaningful maintenance concern.

Repo issue activity

There are no open issues or pull requests, and no issue or pull request activity in the last month. This is not inherently negative, but it provides no evidence of an active community or ongoing support.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher. Low popularity does not make a package unsafe by itself, but it means there is little visible community support if maintenance stops.