univapay-apimatic/univapay-apimatic-sdk

Release historycaution

The package is only 64 days old with four releases, and releases were made in very quick succession. This shows active initial publishing but provides little evidence of long-term maintenance.

Repo bus factorcaution

All three recent commits came from one contributor. Organization ownership provides some handoff capacity, but no second active contributor is shown, leaving maintenance concentrated.

Repo commit activitycaution

The repository had three commits in the last three months, showing some recent activity but a modest maintenance cadence.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are configured. The missing scanning coverage is a transparency and maintenance gap, though it is not by itself a reason to reject the SDK.

Security policycaution

The repository has no SECURITY.md or other detected security policy. For a payment API client, the lack of a clear vulnerability-reporting process is a meaningful hygiene gap.