ironbound/wp-settings-api

Release historydanger

The latest of only three releases was published in October 2015, with no releases in nearly 11 years. This is strong evidence of abandonment risk despite the stable release version.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push in October 2015. No provided signal shows recent maintenance to offset this.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little evidence of a broad user or contributor base. Popularity is supporting evidence, so this modestly reinforces the maintenance concern rather than deciding it alone.

Repo toolingcaution

Composer is used as a build tool, which fits the package ecosystem. No security scanning tools were detected, a minor hygiene gap that does not outweigh the maintenance evidence.

Security policycaution

The repository has no security policy, leaving no documented channel or process for vulnerability reports. This is a transparency gap, though it is secondary to the much older maintenance signal.