atomcoder/laravel-toasty

Maintainerscaution

Only one registry account has publishing access. That is a meaningful continuity risk for a young package, although access records do not prove whether other contributors maintain the source project.

Project backingcaution

The registry namespace is atomcoder while the repository belongs to the individual RichieMcMullen, indicating no demonstrated organizational backing. The package can still be healthy, but this limits apparent continuity beyond the individual owner.

Release historycaution

This is a 156-day-old package with only one release, so there is too little release history to establish durable maintenance or compatibility patterns.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers over the last three months, which is the strongest concern because the package has only one release and its maintenance pattern is not yet established.

Repo issue activitycaution

There are no open issues or pull requests and no activity in the last month. This avoids an unresolved backlog but also shows no recent community or maintainer engagement.