imagewize/aviendha

Usable with caveats: the release is actively maintained, licensed, and backed by a matching organization repository, but all recent commits come from one contributor and the repository lacks security scanning and a security policy.

Latest v1.18.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Package scaffolding

The artifact includes a substantial README and changelog, and the repository uses GitHub Releases, but neither the package nor repository contains tests. For a WordPress theme this is a maintenance gap, though the documentation and release process partly compensate.

Repo bus factor

One contributor made all 132 commits in the last three months, 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, so there is no external adoption evidence; this is a supporting weakness rather than a health verdict because the project is very new.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving a gap in automated supply-chain and code-health checks.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.