uniq

Release historydanger

The latest release was in May 2014, over 12 years ago, and there have been no releases in the last 12 months. This strongly lowers confidence that fixes will arrive, despite the package's small and stable scope.

Repo commit activitydanger

There were no commits or active maintainers in the last three months. Combined with the old release history, this indicates a currently inactive project and raises abandonment risk.

Project backingcaution

The repository is owned by an individual rather than an organization, so the single registry maintainer is consistent with the project's backing but leaves a thin support base.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while five issues and five pull requests remain open. This suggests little recent project attention.

Repo toolingcaution

The repository uses no build tooling or security scanning. That is a modest transparency and maintenance gap, though the package is a six-file, dependency-free utility.