ctocn/junit-laravel

The single maintainer and minimal project activity leave little evidence of ongoing support. A license, matching repository, and release notes improve transparency, but do not offset the long period without another release.

Latest v1.0

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published in November 2021, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency released nearly five years ago.

Maintainers

Only one registry account has publish access, limiting the visible publishing base and increasing continuity risk. No organizational backing is shown to compensate for that thin maintainer base.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these counters provide no supporting evidence of an active user or contributor community.

Repo tooling

Composer is used as the build tool, but no security scanning tools are reported. The missing scanning is a modest hygiene gap and does not by itself establish that the package is unsafe.

Security policy

The source repository has no security policy, leaving reporting and response expectations undocumented. This is a transparency gap, though it is secondary to the much stronger maintenance concern.