magenuts/core-module

Clear licensing, a small dependency surface, and release notes improve transparency. The project otherwise provides little evidence of ongoing maintenance or security practice, so pinning this old release carries substantial liability.

Latest 1.0.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published more than seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a maintained Magento module.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the stale release history and materially increasing maintenance risk.

Repo package mention

The repository name does not match the package name and its README does not mention the package, so ownership of the published package is less transparent than expected.

Repo tooling

The project uses Composer, which supports reproducible PHP packaging, but it has no detected security scanning tools. The missing scanning is a modest hygiene gap rather than proof of unsafe code.

Security policy

The linked repository has no security policy. This is a transparency gap, especially for a module used in an administrative Magento context.