tamara-solution/magento

Healthy and suitable to use, with a thin recent contributor base as the main caveat. It has frequent releases, current repository activity, clear licensing, tests, and organization backing, though the repository lacks security scanning and a security policy.

Latest 2.13.2

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All recent commits came from one contributor, creating concentration risk. Organization backing partly compensates, but no second active contributor is shown in this signal.

Repo commit activity

There was one commit in the last 3 months by one active maintainer. Recent activity exists, but the low volume is a maintenance caution despite the package's frequent release history.

Repo issue activity

The repository has 4 open issues and 1 open pull request, but no issues or pull requests were opened or closed in the last month. This is a modest sign that support activity may be limited.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The missing scanning lowers transparency somewhat, while the package's tests, releases, and current activity provide partial compensation.

Security policy

The repository has no security policy. That leaves vulnerability-reporting expectations unclear, although this is a hygiene gap rather than evidence of abandonment.