sualko/version

Release historydanger

The package has only two releases, both published about eight years ago, with none in the last 12 months. This is strong evidence of abandonment risk, although a tiny stable package may need few releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observable current maintenance.

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 no meaningful community-maintenance buffer.

Repo toolingcaution

Composer is used for build or dependency management, but no security-scanning tools are present. The missing scanner is a modest hygiene gap, not a standalone adoption blocker.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This adds a transparency concern alongside the lack of recent activity.