wemakecustom/wp-config-manager

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement specified. This is a severe adoption risk because the registry itself signals that the package should no longer be depended on.

Release historydanger

The latest release was published in January 2015, and there were zero releases in the last 12 months. More than 11 years without a release is strong evidence of abandonment.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months. This provides no evidence of current maintenance capacity and reinforces the stale release history.

Package scaffoldingcaution

The artifact includes a short README, which provides basic consumer context, but it explicitly says documentation is still a TODO and the project has no tests or changelog. The missing tests and changelog are not expected in every published artifact, while the weak README remains a minor transparency gap for a library.

Repo toolingcaution

The repository uses Composer, providing basic build tooling, but has no security scanning tools. Composer is a modest positive; the lack of scanning is a minor hygiene concern rather than the main adoption blocker.