inespay-payments/api-payflow

Maintainerscaution

Only one account has registry publishing access, which limits publishing redundancy. However, the package is associated with a matching source repository and organization namespace, so this is a modest concern rather than evidence of abandonment.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the last three months, which is a meaningful maintenance concern despite the recent registry release.

Repo popularitycaution

The repository has only 1 star and no forks, so there is little public adoption evidence. Low popularity is supporting context rather than a health verdict for a small SDK.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. This weakens development hygiene, although the absence of scanning alone does not make the release unfit to use.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented for a payment SDK.