afterflow/recipe

Release historydanger

Only two releases were published, both in February 2020, with no releases in the last 12 months. This is strong evidence of abandonment risk, although the package is not deprecated.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with a project whose latest visible activity is several years old. This materially increases maintenance risk.

Repo toolingcaution

The repository uses Composer, but no security-scanning tools were detected. The missing scanning layer is a hygiene gap, though it does not by itself show that the package is unsafe to depend on.

Security policycaution

No security policy was found in the repository, reducing transparency around vulnerability reporting and response. The organization-backed repository provides some context but does not replace a documented process.

Version stabilitycaution

Version 0.1.0 is not a stable major release, which limits maturity evidence. It is not marked as a prerelease, so this is a modest concern rather than a severe release warning.