badcow/dns

Repo bus factorcaution

All four recent commits came from one contributor, so maintenance currently depends heavily on a single active person. Organization ownership provides some handoff capacity but does not remove the concentration risk.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest transparency and maintenance gap rather than evidence of unsafe behavior.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for a library that handles DNS data.

Workflow auditcaution

The only workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both referenced actions are unpinned, which weakens build reproducibility and supply-chain hygiene.