phunkie/effect

Repo bus factorcaution

All 4 recent commits came from one contributor, leaving maintenance dependent on a single active individual. Organization backing helps somewhat but does not remove the concentration risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving a gap in automated security hygiene.

Security policycaution

The repository has no security policy, so there is no documented process for reporting and handling vulnerabilities.

Workflow auditcaution

The only workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, but all 8 action references are unpinned. That weakens build reproducibility and supply-chain hygiene.