Package Health/maxserv/composer-application-context

maxserv/composer-application-context

Its README, tiny four-file tree, and single runtime dependency make the plugin straightforward to inspect and integrate. The lack of a license and security policy adds adoption friction, while the project shows no recent maintenance.

Latest 1.0.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

License

No license is declared, and neither the package nor linked repository contains a recognised license file. This creates a real legal and adoption concern.

Release history

The latest release was published about six and a half years ago, and there have been no releases in the last 12 months. Only three releases exist, indicating a project whose maintenance may have stopped.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.

Repo popularity

The repository has zero stars and forks and only three watchers. Popularity is supporting evidence rather than a verdict, but this provides little evidence of broad community oversight.

Repo tooling

Composer is used as a build tool, but no security scanning tools were detected. The small project is easy to inspect, though automated security coverage is absent.