rick20/faspay

Release historydanger

This package has had only one release, published about 9 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long period without releases. No provided maintenance signal compensates for this inactivity.

Licensecaution

No license is declared, and neither the package nor the linked repository contains a license file. This creates a real adoption and redistribution concern.

Maintainerscaution

The registry lists one maintainer account, and the project is backed by an individual rather than an organization. That leaves limited visible maintenance capacity, especially alongside the inactive repository.

Repo toolingcaution

Composer is used for the build, but no security-scanning tools are present. The missing scanning is a modest hygiene concern for a package handling payment-gateway integration.