juizmill/wp-base

Release historydanger

The package has had only 3 releases, all concentrated in June 2014, with no release in about 12 years. This strongly indicates abandonment risk despite the package not being registry-deprecated.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, following a last repository push about 11 years ago. This is strong evidence that maintenance has stopped.

Repo issue activitycaution

There has been no issue or pull-request activity in the last month, and one pull request remains open. Combined with the inactive commit history, this provides no evidence of current project response.

Repo popularitycaution

The repository has 1 star, 2 forks, and no watchers, indicating very limited adoption. Popularity is supporting evidence rather than a verdict, but it does not offset the maintenance concerns.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap.