carono/tzmonster-api

The MIT license, included tests, and small dependency set make the package straightforward to inspect and integrate. Its maintenance and security practices are too stale for a dependable new dependency, with no recent activity or security policy.

Latest 0.9.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only 2 releases, both from November 2017, and none in the last 12 months; the latest release is nearly nine years old. This is strong evidence of abandonment, though the package is not marked deprecated.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last three months, consistent with the nearly nine-year-old last push. This is the clearest abandonment risk in the assessment.

Maintainers

The registry lists one maintainer, and the project backing identifies a user-owned repository rather than an organization. A narrow maintainer base offers little visible resilience if that person is unavailable.

Repo popularity

The repository has 0 stars, 1 fork, and 1 watcher, indicating little observable adoption or community support. Popularity is supporting evidence rather than a verdict, but it provides no compensating maintenance signal here.

Repo tooling

Composer is used for the build, which fits the ecosystem, but no security scanning tools were detected. This is a modest transparency and maintenance-process gap.