adaiasmagdiel/rubik

The package is clearly documented, licensed, and has frequent releases. Automated security coverage is absent, while the source repository remains small and lightly exercised.

Latest v6.0.3

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing account is listed, which leaves a thin publishing and maintenance base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader institutional support.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. This contrasts with the strong release history and raises a meaningful concern about ongoing source maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap for a database library, though it is not evidence of unsafe code by itself.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This reduces transparency for a package that handles database access.