Package Health/uar-daniel-gafitescu/amazon-mws-laravel

uar-daniel-gafitescu/amazon-mws-laravel

Clear licensing, documentation, and tests make the package easier to evaluate. The repository is not archived and dependencies are limited, but the available maintenance evidence is too old for a new integration.

Latest 3.0.5.2

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 15 releases, but the latest was nearly eight years ago and there were no releases in the last 12 months. This is strong evidence of abandonment risk for a Laravel integration package.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old last-pushed date, this indicates that fixes and compatibility updates are unlikely to arrive promptly.

Project backing

The package and repository are owned by the same individual account, so the source appears aligned with the package. Individual ownership is not itself a health problem, but it provides limited organizational continuity.

Repo issue activity

There was no issue or pull-request activity in the last month and no pull requests were merged. This provides no evidence of current community or maintainer response.

Repo tooling

Composer is used for builds, but no security-scanning tools were detected. The absence of scanning is a hygiene gap, though it is less important than the package's stale maintenance record.