smronju/nativephp-charts

Usable with caveats: the package is clearly licensed, documented, tested, and not deprecated, but it is brand new with only two releases and no observed commit activity yet. Its single-maintainer project also has no security policy or scanning, so long-term maintenance is unproven.

Latest 1.1.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Maintainers

Only one account has registry publish access. This is a real continuity risk for a user-owned project because there is no demonstrated maintainer redundancy.

Project backing

The registry namespace and repository owner match, but the repository is owned by an individual rather than an organization. That is consistent ownership, though it offers less backing than an established project organization.

Release history

This package is extremely new: it was first released today and has only two releases, so there is not enough history to establish durable maintenance or release practices.

Repo commit activity

The repository records zero commits and zero active maintainers in the last three months. Because the project is brand new, this is more a lack of maintenance evidence than proof of abandonment, but it leaves long-term support unproven.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. That is a transparency and maintenance gap for a package intended to be installed as a dependency.