ivmelo/suap-api-php

A clear README, tests, MIT licensing, and a matching source repository make integration and ownership reasonably transparent. The main concern is that the last registry release was in May 2017 and recent repository activity is absent, so maintenance should be verified before adoption.

Latest v1.0.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no registry release in over nine years, despite 16 releases overall. This strongly lowers confidence that the assessed version is actively maintained.

Repo commit activity

There were no commits and no active maintainers in the measured three-month period. Combined with the old latest release, this is meaningful abandonment risk.

Project backing

The registry namespace and repository are owned by the same individual account. This is consistent ownership, but it does not provide organizational backing to compensate for the thin maintenance base.

Repo tooling

Composer is used as a build tool, but no security scanning tool was detected. The missing scanning is a modest hygiene gap, not evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package handling API authentication.