3f/pygmentize

The package is clearly identified, licensed, documented, and has only one runtime dependency. Its single-maintainer project has had no recorded commit activity for over eight years, so future fixes are uncertain.

Latest 1.3

Packagist

52%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The last release was on November 15, 2017, with no releases in the past 12 months. This long gap materially raises abandonment risk despite four historical releases.

Maintainers

One registry account has publish access, leaving little visible publishing redundancy. This is a concern for continuity, although the package is a small, focused wrapper.

Project backing

The repository is owned by an individual rather than an organization, so there is no visible organizational backing to compensate for the narrow maintainer base.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the project having been inactive since 2017. That weakens confidence that defects or compatibility issues will be addressed.

Repo tooling

Composer is used as the build tool, which fits the PHP package ecosystem. No security scanning tool is configured, a minor hygiene gap for a project that has otherwise seen no recent activity.