betstore/laravel-dto

Maintainerscaution

Only one account has registry publish access, leaving limited publishing redundancy. The frequent release history partly offsets this concern by showing that the account is actively maintaining the package.

Project backingcaution

The repository owner is an individual user rather than an organization, so there is no observed organizational backing to broaden maintainer capacity. This is partly offset by the active release history.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no community adoption evidence. Popularity is supporting evidence rather than a requirement, so this is a modest concern rather than a health verdict.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This weakens automated security hygiene without indicating abandonment.

Security policycaution

The repository has no documented security policy. That limits transparency around vulnerability reporting and response expectations.