occ2/progress-bar

Clear licensing and usage documentation reduce adoption friction. The repository is small and lacks a security policy, so ongoing support would need close monitoring.

Latest 1.0.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest of only three releases was published in October 2017, and there have been no releases in nearly nine years. This is strong evidence of abandonment despite the stable 1.0.2 version.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the nearly nine-year gap since the last push. This materially raises maintenance risk.

Repo popularity

The repository has 0 stars, 1 fork, and 1 watcher, providing little evidence of a broad user or contributor base. Low popularity is supporting caution rather than a verdict by itself.

Repo tooling

Composer is used as a build tool, but no security scanning tools were detected. The build tooling is appropriate for the package, while the missing scanning is a minor hygiene gap.

Security policy

No security policy was found in the repository. For a small library this is a transparency gap, although it does not by itself indicate unsafe code.