ajcastro/scribe-tdd

A single maintainer and no published security policy reduce resilience and transparency. The package is licensed, documented, tested, unarchived, and has no install-time scripts, which supports continued use with care.

Latest v0.6.0

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry maintainer is listed. That is workable for a small user-owned project, but it leaves limited publishing and maintenance redundancy.

Release history

The package has had no release in nearly two years, despite nine releases overall; this is meaningful evidence of slowed maintenance for a dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. This is a concrete maintenance concern, though the repository is not archived and was updated in January 2025.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with five issues and one pull request still open. Together with inactive commits, this suggests limited current responsiveness.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning process weakens maintenance transparency without making the package unfit by itself.