pantheon-quicksilver/sanitize-db

Release historydanger

The latest release was over four years ago, with no releases in the past 12 months. That is a substantial abandonment concern for a package developers may depend on for database sanitization.

Repo commit activitydanger

The repository recorded no commits and no active maintainers during the past three months, consistent with the long gap since the last release. This materially lowers confidence in ongoing maintenance.

Maintainerscaution

Only one account has registry publishing access, which is a thin publishing base. The organization-owned repository provides some compensation, so this is a modest concern rather than a severe one.

Repo toolingcaution

Composer build tooling is present, but the repository has no security scanning tools. That weakens maintenance and vulnerability-detection hygiene, although it does not by itself make the release unfit.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap for a script that handles database contents.