jpuck/qdbp

Release historydanger

The package has had no release in more than eight years and no releases in the last 12 months, indicating a strong abandonment risk despite 24 historical releases.

Repo commit activitydanger

There have been zero commits and zero active maintainers in the last three months, consistent with the release history showing prolonged inactivity.

Repo issue activitycaution

Seven issues remain open, with no issues or pull requests opened or closed in the last month, reinforcing the lack of active maintenance.

Repo toolingcaution

The repository uses Composer, but it has no security scanning tooling; this is a hygiene gap that matters more when maintenance is already inactive.

Security policycaution

No security policy is present, leaving no documented process for reporting or handling vulnerabilities in a package that has not been maintained recently.