codicastudio/feedback

Its small dependency footprint, MIT license, and included tests make integration straightforward. The repository is not archived, but the long gap since release and unresolved pull requests limit confidence in future fixes.

Latest 1.0.0

Packagist

48%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published about six years ago, with no releases in the last 12 months. That is strong evidence of stalled maintenance for a library dependency.

Project backing

The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This gives some ownership consistency but limited evidence of a larger maintenance team.

Repo issue activity

There are 20 open pull requests but no new or merged pull requests in the last month. The unresolved backlog is a concrete sign that project changes are not being actively processed.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of a broad community that could sustain the package.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. That is a modest transparency and maintenance gap, not a severe risk on its own.