ceniver/laravel-blog

The package has clear installation documentation and a matching source repository. Its single-person ownership and lack of security tooling leave less evidence of long-term support.

Latest v1.2.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers during the last three months, despite the repository being only about six months old. This is the strongest evidence of stalled maintenance.

Maintainers

Only one registry account has publish access, and the repository owner is an individual rather than an organization. This leaves a thin observable maintainer base.

Project backing

The source repository is owned by an individual account, so the single-maintainer concern is not compensated by organization backing.

Release history

Fourteen releases were published within roughly five hours, followed by no new release for about six months. This bursty history provides limited evidence of sustained maintenance.

Repo issue activity

There were no new or closed issues or pull requests in the last month. With no commit activity, this offers no evidence of ongoing project engagement.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Ceniver

Direct Dependencies

Dependency	Last Release	Score
illuminate/http Version ^11.0\|^12.0	—	—
illuminate/queue Version ^11.0\|^12.0	—	—
illuminate/routing Version ^11.0\|^12.0	—	—
illuminate/support Version ^11.0\|^12.0	—	—
illuminate/database Version ^11.0\|^12.0	—	—