mradang/mysql

Release historydanger

The package has had only two releases, both in October 2018, with no release in roughly eight years. This is strong evidence of abandonment risk for a library dependency.

Repo commit activitydanger

The repository has recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap and providing no evidence of current maintenance.

Maintainerscaution

One registry maintainer account is responsible for publishing the package. This is not inherently unhealthy, but it leaves a thin publishing base alongside the absence of recent activity.

Repo toolingcaution

Composer is used for the build, but no security-scanning tooling is present. That reduces automated assurance, although it is less significant than the long maintenance gap.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap for a database-access library.