detect-node

Release historydanger

The latest release was published over five years ago, with no releases in the last 12 months. The package has only eight releases overall, indicating a long-standing but inactive release line.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, and its last push was over four years ago. This is strong evidence of abandonment risk.

Build provenancecaution

The release has no build provenance attestation or trusted-publisher metadata. This weakens publication transparency but is not severe enough to make the release unfit by itself.

Maintainerscaution

Only one registry account has publish access. This is a limited publishing base, although registry access alone does not establish the project's actual maintenance capacity.

Repo toolingcaution

The repository reports no build tooling and no security-scanning tooling. For this small six-file package the build gap is understandable, but the lack of security checks reduces transparency.