peterculak/laravel-doctrine

Release historydanger

The latest release was published in September 2014, with no releases in the last 12 months. This long release gap is a serious maintenance concern for a framework integration.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no current maintenance.

Repo toolingcaution

The repository uses Composer, but it has no security scanning tools. This is a secondary hygiene gap; the stronger concern remains the absence of current development activity.

Repository archivedcaution

The repository is not marked archived, which is a positive signal, but its last push was in March 2015 and therefore does not compensate for the prolonged inactivity.

Security policycaution

No security policy is present in the repository, leaving vulnerability-reporting expectations unclear. This adds transparency risk, although the package's age and inactivity are more decisive.