eupago/multibanco

Release historydanger

Only three releases were published, with the latest about eight years ago and none in the last 12 months. This is strong evidence of abandonment risk for a payment integration.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the release history showing that maintenance stopped about eight years ago.

Repo popularitycaution

The repository has no stars and one fork, with two watchers. This provides little evidence of broad community support, though popularity is only supporting evidence.

Repo toolingcaution

Composer is used for builds, which is appropriate, but no security scanning tools are present. The missing scanning reduces assurance but does not by itself make the package unfit.

Security policycaution

The repository has no security policy, leaving no documented route for reporting vulnerabilities. This is a meaningful transparency gap for payment-related software.