Package Health/brisum/wordpress-module-post-type-faq

brisum/wordpress-module-post-type-faq

The MIT license and matching repository make the source clear, but the tiny README and absent security policy limit confidence for adoption. No tests or security scanning are reported, leaving little evidence of ongoing quality controls.

Latest 0.0.1

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published over 8 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk.

Package scaffolding

The package includes a README, but it is only 33 characters long and provides no tests, changelog, or release notes. Missing tests and changelog are normal for published artifacts, while the minimal README limits consumer transparency.

Project backing

The registry namespace and repository are owned by the same individual account, so the package has clear ownership but no demonstrated organizational backing.

Repo popularity

The repository has 0 stars and 0 forks, with 1 watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no meaningful external adoption signal.

Repo tooling

Composer is used for the build, which is appropriate, but no security scanning tools are reported. This is a modest transparency and maintenance gap rather than a severe risk.