bahricanli/whatsapp-bridge

Repo bus factorcaution

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

Repo popularitycaution

The repository has zero stars, forks, and watchers. This is weak supporting evidence, but popularity alone does not outweigh the active release and repository signals.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool is reported. The missing scanner is a transparency and hygiene gap rather than evidence of unsafe code.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a minor transparency concern for a package that sends messages through an external bridge.

Workflow auditcaution

The single workflow was fully analyzed with no untrusted checkouts, script injection, or audit findings, and it avoids broad top-level write permissions. Both action references are unpinned, which weakens build reproducibility and supply-chain hygiene.