imi/imi_groupmounts

Release historydanger

Only two releases were published, both in July 2016, with no releases in the last 12 months and about 10 years since the latest release. This is a strong abandonment concern for a dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the roughly 10-year release gap and materially increasing abandonment risk.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month. With no open issues, this is not a direct defect, but it provides no evidence of current maintenance.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are present. This is a modest transparency and hygiene gap, especially alongside the long period without activity.

Security policycaution

The repository has no security policy, leaving no documented reporting or response process. This is a minor transparency gap rather than evidence of an immediate failure.