staudenmeir/eloquent-has-many-deep

Repo commit activitycaution

There were no commits or active maintainers in the preceding three months, which is a maintenance caution. However, the repository was pushed for this release and the release history shows five releases in the last year, partly compensating for the short-term lull.

Repo toolingcaution

Composer is used for builds, but no security scanning tool was detected. The missing scanning is a modest transparency and hygiene gap rather than evidence of abandonment.

Security policycaution

The repository has no published security policy, leaving vulnerability-reporting expectations unclear. This is a documentation gap, not a direct indication that the release is unsafe to depend on.

Workflow auditcaution

Both workflows were fully analyzed with no dangerous triggers, untrusted checkouts, injection findings, or write-wide permissions. However, all five referenced actions are unpinned, leaving workflow dependencies exposed to mutable upstream changes.