n-singularity/async

Release historydanger

Only two releases were published, with the latest nearly seven years ago and none in the last 12 months. This is strong evidence of abandonment for a framework integration.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving compatibility work unsupported.

Project backingcaution

The registry and repository are owned by the same individual account rather than an organization, so the project has limited visible backing capacity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little external evidence of maturity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap, not a severe risk on its own.