ltsc/iaop

The only release is still beta, with no security policy and almost no visible adoption. Its dependency footprint is small and the package includes tests and a usable README, but those positives do not offset the long-term maintenance risk.

Latest 1.0-beta

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published over seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project that has not been maintained since its initial release.

Repo package mention

The repository name does not match the package name and its README does not mention the package, so the linkage is less transparent even though the repository contains the package files.

Repo popularity

The repository has zero stars and forks and only one watcher, providing little evidence of an active user or contributor community. Popularity is supporting evidence, but this further limits confidence in ongoing support.

Repo tooling

Composer is used for the build, which is appropriate for a Packagist package, but no security scanning tooling is present. This is a modest transparency and maintenance gap.