socialdept/atp-client

Repo bus factorcaution

One contributor made all 13 commits in the last three months, creating a significant continuity and abandonment risk. Organization ownership provides some potential handoff capacity, but no second active contributor is shown.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 0 watchers. Popularity is supporting evidence rather than a verdict, but these low counters provide little external validation.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are detected. The build setup is appropriate, while the absent scanning coverage is a transparency and assurance gap.

Security policycaution

The repository has no SECURITY.md or other detected security policy, leaving vulnerability reporting and response expectations undocumented.

Token permissionscaution

Neither workflow declares top-level token permissions. No write permissions are explicitly requested, but the absence of least-privilege declarations is a CI hardening gap.