Package Health/saaaaaaaaasha/ubackupparser

saaaaaaaaasha/ubackupparser

The MIT license and small Composer dependency profile make the package straightforward to inspect and integrate. Its short documentation, lack of tests, and absent security policy leave important maintenance and usage questions unanswered.

Latest 1.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published more than 10 years ago, with no releases in the last 12 months. The stable 1.0.0 version avoids prerelease risk but does not offset the prolonged lack of updates.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the last push occurring in April 2016. This is strong evidence of abandonment risk.

Package scaffolding

The artifact includes a README and changelog, but the README is only 184 characters and contains placeholder installation and usage text; the repository also has no tests. The changelog is a small positive, but consumer guidance and verification remain weak.

Repo tooling

Composer is used for the build, but no security-scanning tools are configured. This is a modest hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, especially for a parser that processes backup data.