brick/date-time-doctrine

Repo commit activitycaution

Only one commit occurred in the last three months and no active maintainers were detected in that period. This is a meaningful maintenance-capacity concern, despite the recent repository push and release history.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of abandonment.

Security policycaution

The repository has no security policy. That weakens vulnerability-reporting transparency, although it does not by itself indicate that the package is unsafe to depend on.

Version stabilitycaution

Version 0.6.0 is not yet at a stable major version, so compatibility expectations are less established. It is not a prerelease, and recent prerelease share is zero, which partly offsets that concern.

Workflow auditcaution

The single workflow was fully analyzed with no untrusted checkouts, injection findings, or excessive top-level permissions. However, all 8 action references are unpinned, leaving build inputs less reproducible and auditable.