pollora/hook

Healthy and reasonable to adopt, with a young project and a narrow active contributor base as the main caveats. It has recent releases, tests, clear source backing, minimal runtime dependencies, and no deprecation or dangerous workflow findings.

Latest v1.1.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Repo bus factor

All three recent commits came from one contributor, creating a real continuity risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence for maturity, but the package is only 86 days old and popularity alone does not outweigh its active releases and organization backing.

Repo tooling

The repository uses Composer build tooling, but no security scanning tools were detected; this is a transparency and maintenance gap rather than evidence of an unsafe release.

Security policy

No repository security policy was found, leaving vulnerability-reporting expectations unclear for a package intended for integration into WordPress projects.

Token permissions

All three workflows omit top-level token permissions, so their required access is not explicitly constrained. No workflow declares top-level write access, which limits the severity of this gap.