merge-source-map

Release historydanger

The package has had no release since December 2017, nearly 9 years ago, despite six releases overall. This is strong evidence of abandonment risk for a dependency that may need ongoing compatibility fixes.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months. Combined with the old latest release, this materially increases abandonment risk.

Maintainerscaution

Only one registry maintainer is listed, and the repository owner is an individual rather than an organization. This leaves limited visible succession capacity.

Repo issue activitycaution

There has been no issue or pull-request activity in the last month, with two open issues and one open pull request. This is consistent with a minimally maintained project.

Repo toolingcaution

The repository uses a build tool, but no security scanning tools were detected. For this small, mature package this is a transparency and hygiene gap rather than a severe risk.