coercive/xml

It has a clear README, matching repository, MIT license, and no install-time scripts. The single maintainer, one-star repository, and lack of security scanning leave limited evidence of ongoing support.

Latest 0.1.20

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published over four years ago, and there were no releases in the last 12 months. Its 30 releases show past activity, but the current gap is a significant abandonment concern.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the long release gap, this is strong evidence that ongoing maintenance is limited.

Project backing

The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to offset the single-maintainer and inactivity concerns.

Repo popularity

The repository has one star, no forks, and two watchers, offering little community evidence to compensate for the lack of recent maintainer activity.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a transparency and hygiene gap, though it is not evidence of maliciousness.