sebkln/content-slug

The repository has no security policy or security-scanning tooling, and issue activity has been quiet recently. Clear release notes, a documented package, a modest dependency set, and an active release history provide useful transparency.

Latest 6.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All 5 recent commits came from one contributor, giving the project a single-person maintenance dependency. The repository is user-owned rather than organization-owned, so there is no provided backing signal to offset that concentration.

Repo issue activity

There are 2 open issues and 1 open pull request, but no new or closed issues or pull requests in the last month. This indicates limited recent community and issue-management activity.

Repo tooling

Composer is used for the build, but no security-scanning tools were detected. For a framework extension, that is a meaningful transparency and maintenance gap.

Security policy

The repository has no security policy. This weakens the documented process for reporting and handling vulnerabilities, although it does not by itself show that the package is unsafe.