Package Health/gregrickaby/nextjs-wordpress-theme

gregrickaby/nextjs-wordpress-theme

The MIT license, release notes, and matching repository make the package transparent and straightforward to consume. Maintenance evidence is thin, with only two releases, no registry release in nearly three years, no recent commits, and no security policy.

Latest 1.0.1

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both around the initial launch, and there have been no releases in nearly three years. That is a meaningful maintenance concern for a package developers may need to track over time.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long registry release gap, this is evidence of slow maintenance.

Repo issue activity

There are no new or closed issues in the last month and two open pull requests remain unmerged. This suggests limited ongoing collaboration, though the project has no open issues.

Repo popularity

With two stars, one fork, and one watcher, the project has little visible community adoption. Popularity is supporting evidence rather than a verdict, but this leaves limited external validation.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing scanner is a hygiene gap rather than evidence that the release is unsafe.