danielmlozano/laravel-conekta

Project backingcaution

The registry namespace and repository owner match, and the repository is user-owned rather than organizationally backed. The matching ownership provides useful continuity, but there is no organization-level backing to offset the thin maintenance evidence.

Release historycaution

The latest release was published nearly four years ago, and there were no releases in the last 12 months. The package had five releases overall, so this indicates materially reduced maintenance activity.

Repo popularitycaution

The repository has only one star and no forks, indicating very limited independent adoption. Popularity is supporting evidence rather than decisive on its own, but it adds caution alongside the stale release history.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. This is a transparency and maintenance gap, though it is less severe because no dangerous workflows are configured.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear for a package that handles payment integrations.