bluebird

Release historydanger

The package has a long history and 228 releases, but its latest release was nearly seven years ago and there were no releases in the last 12 months. That substantially increases the risk that bugs or compatibility issues will remain unresolved.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with no registry releases for nearly seven years, this indicates that ongoing maintenance capacity is currently weak.

Build provenancecaution

No build attestation, trusted publisher identity, or staged publishing is recorded. This reduces release transparency, although the package structure and matching repository provide some compensating context.

Lifecycle scriptscaution

A prepublish lifecycle script is present, so installation or publication behavior deserves review. This is a limited supply-chain hygiene concern rather than evidence that the release is unfit.

Maintainerscaution

Only one registry account has publish access. That is a narrow publishing base, but the linked repository is owned by the same individual and the repository history shows a long-established project, partly compensating for the concentration.