aftandilmmd/laravel-workflow-automation

Maintainerscaution

Only one registry account has publish access. That is a modest publishing bus factor, although repository activity shows a second active contributor and the linked source is directly maintained by the same owner.

Project backingcaution

The repository is owned by an individual account, not an organization, so the highly concentrated commit activity is not offset by clear organizational handoff capacity.

Repo bus factorcaution

One contributor made 29 of 30 commits in the last three months, so maintenance is highly concentrated. A second contributor is active, but the 97% concentration still creates continuity risk for an individual-owned project.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. This is a moderate transparency and hygiene gap rather than evidence of unsafe code.

Security policycaution

The repository has no security policy. For a workflow engine that handles credentials and application integrations, this weakens vulnerability-reporting transparency.