scmp

Registry deprecationdanger

The entire package is deprecated, with npm explicitly directing users to Node.js's crypto.timingSafeEqual(); this is a direct indication that new dependencies should not adopt it.

Release historydanger

The latest release was in December 2019, nearly seven years before collection, and there were no releases in the preceding 12 months. The long release gap reinforces the abandonment concern.

Repo commit activitydanger

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

Repository archiveddanger

The linked source repository is archived, which sharply limits expected maintenance and makes future fixes or compatibility work unlikely despite a recorded push in December 2025.

Security policycaution

No security policy was found in the linked repository, leaving security reporting and response expectations undocumented for a package intended to address timing-attack concerns.