ride/lib-api

Release historydanger

The last release was in October 2016, with no releases in the past 12 months and only three releases overall. This is strong evidence of abandonment for a library dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the last repository push occurring in 2016. This materially increases abandonment risk.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are present. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. For an inactive library, this adds a meaningful maintenance gap.