mkgor/beautiful-errors

The README, MIT license, and lack of install scripts make the package straightforward to evaluate and integrate. Its tiny repository and absent security policy provide little evidence of ongoing care, so pinning this release carries abandonment risk.

Latest 1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about six years and four months ago, with no releases in the last 12 months. This is strong evidence of a dormant project.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. While a clean tracker is not inherently unhealthy, it offers no evidence of current project engagement alongside the stale release history.

Repo popularity

The repository has 1 star, 1 fork, and no watchers, indicating very limited adoption or community oversight. Popularity is supporting evidence, but here it adds to the broader abandonment concern.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a modest transparency gap rather than a severe risk.

Repository archived

The repository is not archived, but it was last pushed about six years and four months ago, matching the single-release history and reinforcing the maintenance concern.