davidvandertuijn/laravel-after-seeders

Maintainerscaution

Only one registry maintainer is listed, which creates a thin publishing and support base. The linked repository is owned by the same individual, so this is consistent project backing rather than an unexplained registry mismatch.

Release historycaution

The package has made no releases in the last 12 months, and its latest release was nearly two years ago. The five-release history shows a real project but does not demonstrate current maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern, although the package is small and its latest release remains stable.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are reported. That limits visible supply-chain and dependency hygiene.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap rather than evidence that the package is unsafe.