backo2

Release historydanger

Only two releases exist, both from November 2014, with no release in nearly 12 years. This strongly raises abandonment risk despite the package being mature enough to have a stable 1.0.2 release.

Repo commit activitydanger

The repository has recorded zero commits and zero active maintainers in the last three months, consistent with its last push being more than seven years ago. That leaves little evidence of current maintenance.

Maintainerscaution

One registry account has publish access, which gives the package a thin apparent publishing base. This is a concern alongside the inactive repository, though registry access alone does not establish who actively maintains it.

Repo package mentioncaution

The linked repository name does not match backo2 and its README does not mention backo2, so the repository may not clearly represent this package. This weakens transparency for adopters.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. For an old dependency with no recent activity, this is a genuine oversight gap.