faulkj/boclient

Release historydanger

The package has had no release in 3 years and 8 months, with only three releases overall and none in the last 12 months. That is strong evidence of abandonment risk for a client library.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last 3 months, providing no evidence of ongoing maintenance to offset the long release gap.

Maintainerscaution

Only one registry maintainer is listed, leaving limited visible publishing capacity. The linked repository is user-owned, so there is no organizational backing signal to compensate for that thin base.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. That weakens maintenance hygiene for a package handling authenticated web-service access.

Security policycaution

The linked repository has no security policy, which reduces transparency about vulnerability reporting and maintenance expectations. This is a meaningful oversight gap, though not a severe risk by itself.