Package Health/wpelevator/vendor-isolator

wpelevator/vendor-isolator

This release is usable but carries meaningful maintenance and maturity risk. It is not deprecated or archived, has a matching repository, a clear MIT declaration, recent publication activity, and organization backing. However, the project has only three releases across nearly two years, just one commit from one contributor in the last three months, no tests or changelog, no security policy or scanning, and very limited repository adoption. The small, focused package and organization ownership reduce some concerns, but the thin validation and contributor activity warrant caution before making it a critical dependency.

Latest 0.1.1

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A reasonably detailed README explains the Composer plugin's behavior and limitations, but neither the artifact nor repository contains tests or a changelog. For a code-transforming Composer plugin, the absence of tests is a genuine maturity gap.

Release history

Only three releases have been published over 693 days, with one release in the last 12 months and a median interval of about 347 days. This indicates a slow release cadence and limited evidence of sustained maintenance.

Repo bus factor

All recent commits come from one contributor, creating a concentrated bus factor. Organization ownership provides some ability to hand maintenance off, but no second active contributor is shown.

Repo commit activity

Only one commit was recorded in the last three months from one active maintainer. Recent activity exists, but it is too sparse to demonstrate a robust maintenance pace.

Repo issue activity

There were no new or closed issues in the last month and no merged pull requests, with one open pull request. This provides little evidence of an active feedback or review process.