mygento/base

Release historydanger

The latest release was in November 2018, with no releases in the past 12 months. That long gap is strong evidence of abandonment risk for a dependency released at version 2.2.16.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the past three months, reinforcing the stale release history rather than showing active maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance-hygiene gap, not evidence that the release is unsafe by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This adds a minor transparency concern alongside the stronger evidence of inactivity.