leafs/alchemy

Repo bus factorcaution

All 33 recent commits came from one contributor, creating a real continuity risk. Organization backing provides some handoff capacity, but no second active contributor is shown.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and assurance gap.

Security policycaution

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

Token permissionscaution

Neither workflow declares top-level token permissions. No write permissions were observed, but explicit least-privilege configuration would provide stronger assurance.