sevaske/zatca-api

Testing and documentation are solid, and the package has a clear license and regular release history. Recent repository activity has stopped, while security scanning is absent and workflow actions are unpinned; adoption should account for the single-maintainer project.

Latest 2.0.2

Packagist

66%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account can publish releases, limiting publishing redundancy. The matching repository owner and observed release activity provide some compensation, but not a second maintainer.

Project backing

The registry namespace and repository are owned by the same individual account, providing direct ownership alignment but no organizational backing or redundancy.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, a meaningful sign that maintenance may have slowed despite recent releases.

Repo popularity

The repository has five stars and four forks, indicating a small user base. Popularity is supporting evidence rather than a health verdict, but it offers limited external validation.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing security automation lowers assurance for a package handling API authentication and certificates.