vitalybaev/laravel5-dkim

Release historydanger

The latest release was about six years ago, with no releases in the past 12 months. Its earlier release cadence shows prior activity but does not offset the prolonged pause.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the roughly six-year gap since the last update.

Repo issue activitycaution

There were no new or closed issues or pull requests in the past month, while seven issues and two pull requests remain open. This reinforces the maintenance concern, though it is weaker evidence than the absent commits and releases.

Repo package mentioncaution

The linked repository neither matches the package name nor mentions the package in its README. That makes package ownership less transparent and raises some risk despite the matching namespace and repository owner.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence that the package is unsafe.