jalno/autodiscovery

The MIT license and stable 1.0.1 release are positives, and the workflow audit found no dangerous sinks. However, the project has seen no commits for about five years, has no tests or consumer README, and uses four unpinned actions, leaving maintenance and build-reproducibility concerns.

Latest 1.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has five releases, all clustered in June 2021, with no releases in the last 12 months; this is strong evidence of abandonment risk for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for about five years.

Package scaffolding

The artifact has no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but the missing README reduces integration transparency for a library; the GitHub release confirms some release documentation practice but provides no notes for this version.

Repo popularity

The repository has zero stars, one fork, and one watcher, offering little supporting evidence of adoption or community review. Popularity is only supporting evidence, so this reinforces rather than creates the maintenance concern.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured, leaving a modest repository-hygiene gap.