iionly/gifts

The single maintainer and lack of security scanning provide limited ongoing oversight. Clear licensing, documentation, and a matching source repository help, but the package has not shown recent maintenance.

Latest 2.3.1

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published about eight years ago, with no releases in the last 12 months and only three releases overall. This is substantial abandonment risk for a dependency, despite the package having a long history.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the stale release history. No provided signal shows compensating recent maintenance.

Maintainers

Only one registry publishing maintainer is listed, leaving a thin publishing base and increasing continuity risk. The linked repository is user-owned rather than organization-backed, so there is no provided organizational support to offset this.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. The missing security automation adds a modest maintenance concern alongside the absence of recent activity.

Security policy

The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a meaningful hygiene gap for a plugin that handles application functionality, though it is not evidence of maliciousness.