zortje/mysql-keeper

Release historydanger

The package has had no release in about 11 years, with zero releases in the last 12 months. Four releases were published early in its history, but that does not offset the prolonged release silence.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was about 10 years ago. This is strong evidence of abandonment risk.

Project backingcaution

The package and repository are owned by the same individual account rather than an organization. This is consistent ownership, but it provides no broader organizational backing to offset the thin maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The build setup supports reproducibility, while the missing security tooling leaves a modest hygiene gap.

Security policycaution

The repository has no security policy and no security scanning tools. For a database-inspection library, this is a genuine transparency and maintenance gap, although it is less severe than the long inactivity period.