fuzzyma/contao-eloquent-example-project

Release historydanger

The package has only 2 releases, both from over 10 years ago, and none in the last 12 months. That gives little evidence of ongoing maintenance for a dependency released at version 0.1.1.

Repo commit activitydanger

There were 0 commits and 0 active maintainers in the last 3 months, consistent with the repository's last push being over 10 years ago. This is strong evidence of abandonment risk.

Dependency profilecaution

The project declares 12 runtime dependencies, including an older framework-style application stack, increasing the maintenance burden for a package with no recent releases.

Repo toolingcaution

Composer and Phing provide build tooling, but no security scanning tools are reported. That leaves an avoidable transparency and maintenance gap in an old dependency stack.

Security policycaution

The linked repository has no security policy, so there is no documented process for reporting or handling security issues. This matters more because the project has been inactive for over 10 years.