deepayment/sdk

Release historycaution

The package is only 10 days old but has six releases, with a median interval of about 2 days. This shows active initial development, but there is not yet enough history to demonstrate long-term stability.

Repo bus factorcaution

One contributor made all four recent commits, concentrating maintenance in a single person. Organization ownership provides some backing, but no second active contributor is shown to share the load.

Repo commit activitycaution

Four commits were made in the last three months, all during this very recent project period. Activity is present, but the short history does not yet establish durable maintenance.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. For a payment SDK, that missing security practice is a meaningful hygiene concern.

Security policycaution

The repository has no security policy. That leaves vulnerability reporting and response expectations undocumented for a security-sensitive payment integration.