Package Health/ubermanu/magento2-es-import-map

ubermanu/magento2-es-import-map

The MIT license, focused file tree, and usable README make the package straightforward to inspect and integrate. Single-person ownership, no recent commit activity, and no security policy or scanning reduce maintenance resilience and oversight.

Latest v3.0.0

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository are owned by the same individual account, so there is no organization backing shown to compensate for the thin maintainer base.

Release history

The package has had no release in nearly four years, despite five releases overall; its earlier 18-day median interval shows it was once actively updated. This is a meaningful maintenance concern.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old latest registry release, this points to weak current maintenance capacity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of broad review or adoption.

Repo tooling

Composer is used as the build tool, but no security scanning tools are present. For a small package this is a hygiene gap rather than a severe risk.