aminrafiei/laravel-toon

Clear documentation, tests, licensing, and a matching source repository make integration easier. The single-release history and no commits in the last three months leave maintenance uncertain, while no security policy reduces transparency.

Latest v1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are both owned by the same individual user account. That is coherent ownership, but it offers less organizational backing than a supported team or organization.

Release history

This package has released only once, on 2025-11-28, and has had no subsequent releases over roughly ten months. That makes ongoing maintenance unproven for a dependency.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. For a package less than a year old with one release, this is a meaningful sign that maintenance capacity is not yet demonstrated.

Repo issue activity

There are no open issues or pull requests, and no recent issue or pull-request activity. This is consistent with a small package, but it also provides little evidence of an active user or maintainer community.

Repo tooling

The repository uses Composer for builds, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not evidence that the package is unsafe.