Package Health/jellybool/flarum-ext-slug

jellybool/flarum-ext-slug

Its MIT license, clear package contents, and matching repository make the release transparent to inspect. The small dependency set is manageable, but there are no tests or security policy, and the project shows no recent development activity.

Latest 1.01

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 8 years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained release line.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history and leaving compatibility issues unlikely to be addressed.

Project backing

The repository is owned by the matching individual publisher account rather than an organization. That is consistent with a small personal package but provides little evidence of a broader maintenance team.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. This is a modest process gap rather than evidence of unsafe code by itself.

Security policy

The linked repository has no security policy. For a package that processes application behavior and depends on an external slug service, this weakens vulnerability-reporting transparency.