leafs/db

Repo bus factorcaution

One contributor made all eight commits in the last three months. Organizational backing helps provide ownership context, but no second active contributor is shown, leaving a real continuity concern.

Repo toolingcaution

Composer build tooling is used, but no security scanning tools are reported. That is a moderate transparency gap for a database library, not evidence of an unsafe release by itself.

Security policycaution

The repository has no security policy, so there is no documented security reporting process visible to consumers.

Workflow auditcaution

Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, injection findings, or excessive permissions. However, all four action references are unpinned, which weakens build reproducibility.