torann/api-client

Release historydanger

The latest release was in May 2017, with no releases in the last 12 months despite an established package history. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided maintenance signal offsets this inactivity.

Repo popularitycaution

The repository has only 4 stars, 3 forks, and 1 watcher, indicating limited visible adoption. Popularity is supporting evidence rather than a verdict, but it offers little confidence to offset inactivity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a modest transparency gap, not a severe risk by itself.

Security policycaution

The repository has no security policy. For a client library handling remote-service requests, this reduces transparency around vulnerability reporting and maintenance expectations.