Package Health/src-run/augustus-deprecation-library

src-run/augustus-deprecation-library

Clear licensing, tests, documentation, and a matching organization repository improve transparency. The narrow dependency footprint and lack of install-time scripts also reduce adoption friction, but ongoing maintenance remains the main concern.

Latest 0.7.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published nearly 10 years ago, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment for a library dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months, while the repository was last pushed over 9 years ago. This materially increases the risk that defects and compatibility problems will go unaddressed.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counters provide no meaningful external adoption signal to offset the inactivity.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a standalone reason to reject the package.

Security policy

The repository has no security policy. For a small library this is a hygiene gap, but it is less significant than the long-maintenance gap.