esslassi/metable

MIT licensing, a substantial README, and a package tree that matches the repository improve transparency. The lack of recent security tooling leaves additional maintenance risk for a framework integration.

Latest 2.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made no releases in the last 12 months, and its latest release was about two years ago, indicating prolonged release inactivity.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the extended release pause and suggesting the project is no longer actively maintained.

Maintainers

Only one account has registry publish access. Because the repository is user-owned rather than organization-backed, this represents a thin publishing base and increases continuity risk.

Project backing

The registry namespace and repository are owned by the same individual account, confirming ownership alignment but providing no organizational backing to offset the single-maintainer risk.

Repo popularity

The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of a broad support community.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Esslassi Mohammed

Direct Dependencies

Dependency	Last Release	Score
illuminate/events Version ^8.0\|^9.0\|^10.0\|^11.0	—	—
illuminate/support Version ^8.0\|^9.0\|^10.0\|^11.0	—	—
illuminate/database Version ^8.0\|^9.0\|^10.0\|^11.0	—	—