dbstudios/analyst

The small, focused dependency set, clear README, tests, and MIT licensing make integration straightforward. Maintenance stopped after January 2016, and the repository has no security policy or security-scanning tools, leaving long-term support uncertain.

Latest 2.0.1

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than 10 years: its latest release was January 27, 2016, with three releases overall. This is strong evidence of abandonment despite the package not being deprecated.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, while the last repository push was in January 2016. This is the strongest evidence that the package is abandoned.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational backing shown to compensate for the single registry maintainer and absent recent activity.

Repo popularity

The repository has 12 stars, zero forks, and two watchers, indicating a small user base. Popularity is supporting evidence only and does not outweigh the clear maintenance gap.

Repo tooling

Composer build tooling is present, but no security-scanning tools are reported. The missing security automation adds a modest transparency and maintenance concern for a package that has not been updated in years.