@egjs/hammerjs

Release historydanger

The latest release was published nearly seven years ago, with no releases in the last 12 months; this materially raises abandonment risk despite a history of 10 releases.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with a project that is no longer actively maintained.

Repo issue activitycaution

No issues or pull requests were opened or closed in the last month, with only one open issue; this supports the picture of low current activity.

Repo toolingcaution

The repository uses Rollup, Babel, and npm scripts, but no security scanning tools are reported, leaving a modest transparency and maintenance gap.

Security policycaution

No repository security policy is present, so vulnerability reporting and response expectations are not documented.