@types/crypto-js

Build provenancecaution

No build attestation or trusted-publisher provenance is present, leaving publication origin less transparent, though this is not by itself evidence of an unhealthy project.

Release historycaution

The package has 39 releases and a history of regular publishing, but it has had no release in over two years, which lowers confidence that new ecosystem changes are being tracked.

Repo package mentioncaution

The repository name does not match the package and its README does not mention the package, creating some uncertainty about package-to-repository ownership; the package README does identify the relevant DefinitelyTyped path, which partly compensates.