simonmarcellinden/toast

Release historydanger

The package has had no releases in about five years, with four releases concentrated on its first day. This strongly indicates abandonment risk despite the package not being deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the roughly five-year gap since its last push. No provided signal shows compensating maintenance activity.

Maintainerscaution

Only one registry publishing account is listed, leaving limited visible publishing continuity. The linked repository is user-owned rather than organization-backed, so this is a meaningful resilience concern.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a modest hygiene gap, not evidence that the package is unsafe by itself.

Security policycaution

The repository has no security policy, leaving no documented reporting path or security-maintenance expectations. This adds transparency risk alongside the lack of recent activity.