beautycoding/apiutils

The package is small and clearly identified, with an MIT license and only one runtime dependency. Missing security scanning provides little reassurance for future maintenance.

Latest 1.4.1

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made no releases in about 10 years: all 8 releases were published in March 2016, and there were none in the last 12 months. This strongly suggests abandonment despite the stable version number.

Repo commit activity

The repository has had zero commits and zero active maintainers in the last 3 months, consistent with the release history showing no activity for about 10 years. The repository is not archived, but that does not compensate for the prolonged inactivity.

Repo popularity

The repository has 0 stars and 0 forks, with only 2 watchers. Popularity is supporting evidence rather than a verdict, but these figures provide no meaningful community-maintenance signal.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security-scanning tools are present. The missing scanning is a modest hygiene concern rather than proof of unsafe code.

Security policy

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it is secondary to the long inactivity.