ecomdev/compiler

The repository has a matching name, substantial source and specification files, and no install-time scripts. Its documentation leaves installation and examples unfinished, while the lack of recent maintenance and security policy makes long-term support uncertain.

Latest 1.0.0-alpha

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published over 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a package intended as an application dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the repository having been inactive for over 10 years. This materially raises abandonment risk.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. That is a modest transparency and maintenance gap, not a standalone reason to reject the package.

Repository archived

The repository is not archived, which is a meaningful compensating signal. However, its last push was in 2016, so the unarchived status does not offset the separate evidence of inactivity.

Security policy

The repository has no security policy. For an old dependency with no recent maintenance, the absence of a stated vulnerability-reporting process increases uncertainty about support.