nikapps/nikpay-laravel

Release historydanger

The last release was about eight years ago, with no releases in the past year and only seven releases overall. This makes maintenance and compatibility with current Laravel and PHP versions uncertain.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the last push being about eight years ago. This is strong evidence of abandonment risk.

Dependency profilecaution

The package has six runtime dependencies, including Laravel components and a payment package, creating compatibility surface area that matters for an older Laravel integration. The signal does not show an excessive or clearly unsafe dependency set.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. That leaves security hygiene less visible, although it is secondary to the stronger inactivity concern.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though not as severe as the lack of recent maintenance.