jmleroux/pdf-merger

Release historydanger

Only two releases were published, both in April 2020, with none in the last 12 months; the package has had no new release for over six years. This is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the last repository push being over six years ago. This materially increases abandonment and unpatched-defect risk.

Dependency profilecaution

Five runtime dependencies, including three alternative PDF libraries, create a relatively broad dependency surface for a small merger package. The alternatives are directly related to the documented functionality, so this is only a modest concern.

Project backingcaution

The registry namespace and repository are owned by the same individual account, providing consistent ownership context but no organizational backing to compensate for the thin activity record.

Repo popularitycaution

The repository has only 1 star, 1 fork, and 1 watcher, indicating very limited community visibility or external validation. Small packages can still be healthy, but this provides little compensating evidence for inactivity.