crypto

Registry deprecationdanger

The package is deprecated at registry scope because it is no longer supported and has been replaced by Node's built-in module, making this release unfit for a new dependency.

Release historydanger

The latest release was in August 2017, with zero releases in the last 12 months; this confirms prolonged abandonment rather than an actively maintained dependency.

Repo commit activitydanger

The linked repository had zero commits and zero active maintainers in the last three months, providing no evidence of current maintenance capacity.

Package file treecaution

The published artifact contains only README.md and package.json, which is consistent with a deprecated holder package and provides no implementation to maintain.

Repo package mentioncaution

The linked repository name does not match the package and its README does not mention it, so the source association is weak, although the npm organization backing provides some context.