davispeixoto/laravel-4-solr

Maintainerscaution

Only one registry account has publish access, and the project is backed by an individual rather than an organization. This is a thin maintenance base, though registry access alone does not establish actual activity.

Release historycaution

The package has made no release in over 12 years; only three releases were published, all clustered at the start of the project. This is strong evidence of abandonment risk.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the last 3 months. Combined with the release history, this materially increases abandonment risk.

Repo toolingcaution

Composer is used for builds, but no security scanning tooling is present. That is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters for a package that performs application integration, even though it is not a severe issue by itself.