zawa/getui

The small dependency surface and matching repository make its purpose easy to inspect. Its lack of security tooling and extremely thin project activity leave maintenance and abandonment concerns unresolved.

Latest 1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published in June 2018, with no releases in the last 12 months. This is strong evidence of prolonged inactivity for a dependency released over eight years ago.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and indicating no visible ongoing maintenance.

Repo tooling

Composer is used as the build tool, but no security-scanning tools are present. This is a modest transparency and maintenance gap rather than evidence of an unsafe package.

Repository archived

The repository is not archived, which avoids an explicit abandonment marker, but its last push was in June 2018 and does not offset the prolonged inactivity shown elsewhere.

Security policy

The repository has no security policy. For an SDK that handles communication with an external push service, this weakens vulnerability-reporting transparency.