banbans/laravel-ckeditor

Release historydanger

The latest release was about 8 years ago, with no releases in the last 12 months; this is strong evidence of abandonment risk despite a prior history of three releases.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the package's long release gap and indicating that maintenance has stopped.

Repo popularitycaution

The repository has only 3 stars, no forks, and no watchers, providing little evidence of a broad user or contributor community to compensate for the inactivity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured, so automated detection of dependency or source issues is not evident.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; this is a meaningful transparency gap for a dependency.