jpeg-exif

Registry deprecationdanger

The npm registry marks the entire package as deprecated with a message stating it is no longer supported. This is a severe adoption risk even though no replacement package is specified.

Release historydanger

The package has 20 releases but its latest release was over six years ago, with no releases in the past 12 months. That strongly indicates maintenance has stopped.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, leaving publication origin less verifiable. This is a transparency weakness, though it does not outweigh the explicit deprecation on its own.

Maintainerscaution

One registry account has publish access. This is limited administrative redundancy, but registry access does not establish actual maintenance activity and is outweighed by the release history.

Type declarationscaution

No type declarations are included, which is a minor integration gap for TypeScript consumers but not by itself a maintenance or abandonment risk.