zahran/mapper

Usable with caveats: it is a newly published package with solid documentation, tests, and a matching source repository, but it has no established release or maintenance history yet. Security policy and workflow permission declarations are also missing, so adoption should start cautiously.

Latest 1.0.0

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package is backed by a personal-user repository rather than an organization, so the single registry maintainer reflects a genuinely thin maintainer base. There is no organizational backing to compensate for that concentration.

Release history

This is the first release, published today, so there is no track record for release consistency or long-term maintenance. The repository was pushed recently, but that does not compensate for the absence of release history.

Repo commit activity

There were no commits or active maintainers recorded in the last three months, but the package and repository were created today, making this window too short to establish a collapse in maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. Tests and CI provide some compensation, so this is a modest transparency gap rather than a severe risk.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, although the package's tests and CI provide some compensating project hygiene.