jimp-compact

Repo commit activitydanger

There were no commits and no active maintainers in the three months before collection. Combined with the nearly five-year registry release gap, this is the main abandonment risk.

Release historycaution

There have been 23 releases, but none in the last 12 months and the latest registry release was nearly five years ago. That long publishing gap is a meaningful maintenance concern despite the earlier frequent release cadence.

Repo issue activitycaution

The repository has five open issues and seven open pull requests, but no new or closed issues or pull requests in the last month. This suggests limited current maintenance.

Repo toolingcaution

The repository uses TypeScript, npm scripts, and ncc for its build, supporting a reproducible compilation approach. It has no security scanning tools, which is a modest transparency and maintenance gap.

Security policycaution

The repository has no security policy. This does not make the package unfit, but it leaves vulnerability-reporting expectations unclear.