getgrav/grav-db-kit

The package has clear documentation, repository tests, a changelog, and a simple dependency profile. Its organization backing and clean audit reduce concern, but the project is too new to establish durable maintenance.

Latest 1.0.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This release is from a package only 0 days old with three releases published over roughly 4 hours, so there is not yet enough history to demonstrate sustained maintenance.

Repo commit activity

The repository has zero commits and zero active maintainers in the last 3 months, but it was created only recently, so this is evidence of an unproven history rather than established abandonment.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap for a package handling database and job infrastructure.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but is not a severe risk by itself.

Workflow audit

The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both action references are unpinned, which weakens build reproducibility.