number-to-bn

Release historydanger

The package has eight releases but none in nearly 10 years, with the latest registry release in December 2016; this materially raises maintenance and abandonment concerns.

Build provenancecaution

No build attestation or trusted-publisher provenance is available, reducing publication transparency, though this is not by itself evidence of an unhealthy project.

Lifecycle scriptscaution

A prepublish script is present, adding some build or publishing complexity, but this signal alone does not show unsafe installation behavior.

Maintainerscaution

Only one registry account has publish access, leaving a thin publishing base and increasing continuity risk if that maintainer becomes unavailable.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the single-maintainer publishing risk.