leemason/metable

Tests, documentation, and a clear MIT license make the package transparent. Its single release and no commits for nearly 11 years leave compatibility and maintenance risk unresolved; pinning it should be limited to legacy Laravel applications.

Latest 1.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published nearly 11 years ago, with no releases in the last 12 months. This is strong evidence of stagnation for a dependency whose framework compatibility may change over time.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long gap since its only release. No provided maintenance signal compensates for this inactivity.

Repo popularity

The repository has 3 stars, 0 forks, and 1 watcher, offering little supporting evidence of broad community adoption or external maintenance capacity.

Repo tooling

Composer is used for the build, providing expected ecosystem tooling, but no security scanning tools are present. This is a minor transparency gap rather than a primary adoption blocker.

Security policy

The repository has no security policy. That weakens disclosure transparency, although the small, inactive project and other signals make the long maintenance gap the more important concern.