brick/geo-doctrine

Repo commit activitycaution

There were no commits from any active maintainer in the last three months, which is a real sign of currently quiet development. The two registry releases in the last year and the recent push provide partial compensation, so this lowers confidence in active maintenance without making the package unfit.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. The build setup is established, while security-process coverage is limited.

Security policycaution

The repository has no security policy. This is a transparency and incident-response gap, though it is not evidence that the package is unsafe.

Version stabilitycaution

Version 0.6.0 is not a stable-major release, so consumers should expect possible API changes. It is not marked as a prerelease, which partly offsets that concern.

Workflow auditcaution

The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings, and it does not grant top-level write permissions. However, all 17 action references are unpinned, leaving avoidable dependency-integrity risk.