tomato-technologies/tomato-omipay

Release historydanger

The latest release was published in January 2019, and there have been no releases in the last 12 months despite the package being about seven years old. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its last push. No newer activity compensates for this maintenance concern.

Repo popularitycaution

The repository has zero stars, zero watchers, and one fork. Popularity is only supporting evidence, but these figures provide little evidence of an active user or maintainer community.

Repo toolingcaution

Composer is used for the build, which is appropriate, but no security-scanning tools are configured. This leaves an avoidable maintenance and vulnerability-detection gap.

Security policycaution

The repository has no security policy. That is a transparency gap for a package handling payment integration, although it does not by itself show that the code is unsafe.