onetoweb/multisafepay

Usable with caveats: it is a small, clearly identified MIT-licensed client with documentation and organization backing, but it has had only one release and no repository activity for about two years. Depend on it only if its API is stable enough for your needs and you can maintain it yourself.

Latest v1.0.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 2 years and 1 month ago, with no releases in the last 12 months. This is the clearest sign of limited ongoing maintenance, though it may also reflect a deliberately stable client.

Repo commit activity

There were zero commits and zero active maintainers in the last 3 months, consistent with a repository that has seen no activity since its initial release. This materially raises abandonment and unaddressed-defect risk.

Repo tooling

The repository uses Composer, providing normal project build tooling, but has no security-scanning tools. The missing scanning is a modest transparency gap rather than a severe risk for this small library.

Repository archived

The linked repository is not archived, but it was last pushed about 2 years and 1 month ago. The non-archived status is reassuring, while the age of the last update reinforces the maintenance concern.

Security policy

No security policy is present, leaving the process for reporting and handling vulnerabilities unclear. This matters for an API client, although the organization-backed repository provides some compensating ownership context.