crudadmin/autoajax

The README is clear and the package has a small, understandable dependency surface. It lacks repository tests, security scanning, and a security policy, while recent publishing and organizational backing reduce abandonment concerns.

Latest 2.0.16

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes a substantial README explaining installation and usage, which is important for this integration library. Tests and a changelog are absent from both the package and repository, leaving limited verification and release documentation.

Repo commit activity

There were no commits and no active maintainers in the most recent 3 months. Because the release history shows four releases in the last year and the latest push matches the assessed release, this is a modest maintenance concern rather than strong abandonment evidence.

Repo popularity

The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a requirement, but these counts provide little external adoption evidence.

Repo tooling

The repository uses Composer for builds, which fits the package ecosystem. No security scanning tools are configured, leaving a modest transparency and maintenance gap.

Security policy

The repository has no security policy. This weakens the documented process for reporting and handling vulnerabilities, though it does not by itself show unsafe code or abandonment.