broccoli-node-api

Release historydanger

The latest release was over seven years ago, with no releases in the last 12 months, despite eight releases overall. This strongly raises abandonment risk for a dependency whose definitions may need maintenance as the ecosystem changes.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in 2019. This is strong evidence that maintenance has stopped.

Build provenancecaution

No build attestation or trusted-publisher information is available for the release. This weakens publication transparency, although it is not by itself evidence that the package is unsafe.

Repo issue activitycaution

There are no recent issues or merged pull requests, and one pull request remains open. This is consistent with a dormant project and provides little evidence of active support.

Repo toolingcaution

The repository reports no build tool and no security scanning tools. For a tiny type-only package this is partly understandable, but it leaves limited evidence of validation or ongoing maintenance.