dravencms/logging

Release historycaution

The latest registry release was about four years ago, with no releases in the past 12 months and only three releases overall. This materially raises staleness risk, although recent repository activity provides some compensation.

Repo bus factorcaution

All one recent commit came from a single contributor, creating concentrated maintenance responsibility. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo commit activitycaution

The repository recorded one commit in the past three months, showing some current maintenance despite the long gap since the latest registry release. The activity is very limited, so it only partly offsets the release-history concern.

Security policycaution

The repository has no security policy, reducing transparency about vulnerability reporting and handling. This is a hygiene and maintenance concern rather than evidence that the package is unsafe.