wpdev/odata-feed

Documentation, tests, and a clear license make adoption practical. The project is only 92 days old, and most recent commits come from one contributor; workflow dependencies are also unpinned. No security policy is published, leaving maintenance practices less transparent.

Latest 1.0.0

Packagist

66%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so the highly concentrated contributor activity has no visible organizational handoff support.

Release history

The package is 92 days old and has only one release, so its maintenance record is still unproven. The repository shows 29 commits in the last three months, which provides some compensating activity.

Repo bus factor

One contributor made 26 of 29 recent commits, or about 90%, so maintenance depends heavily on a single person. Two additional contributors provide limited compensation, but the concentration remains a real continuity concern.

Repo tooling

Composer build tooling is present, but no security-scanning tooling is reported. This is a modest transparency and maintenance gap rather than evidence of an unsafe release by itself.

Security policy

The repository has no security policy. That makes vulnerability reporting and response expectations unclear, although it does not by itself show that the package is unmaintained.