itmar/loader-package

Validation and security transparency are limited, with no tests, security policy, or scanning. The release is documented, licensed, and clearly tied to its repository, which offsets some of that concern.

Latest v1.2.2

Packagist

60%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. The linked project is user-owned rather than organization-backed, so there is little visible redundancy if that maintainer stops supporting it.

Package file tree

The four-file package is small and its repository matches the artifact, which is plausible for a focused Composer autoloader, though it provides little visible implementation surface for review.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, indicating that maintenance activity has currently stopped and increasing abandonment risk.

Repo popularity

The repository has zero stars and forks and one watcher. This is weak supporting evidence for maturity, though popularity alone does not determine whether a small package is healthy.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tooling is present, leaving a modest transparency gap.