vavajke/bxcore

Release historydanger

There has been only one release, published over five years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a package intended as an ongoing dependency.

Licensecaution

The manifest declares MIT and license files are present, so the release is licensed, but detected Apache-2.0 and OFL-1.1 text creates a license-scope mismatch that requires clarification.

Maintainerscaution

Only one registry account is listed with publish access. This is not proof of inactive development, but it indicates limited visible continuity when combined with the single-release history.

Package scaffoldingcaution

Tests and a changelog are present, which supports basic project discipline. The missing README is a real usability gap for a package consumers must understand, but it is not by itself an abandonment signal.