moro/container7

Release historydanger

The latest release was about eight years ago, with no releases in the last 12 months; this is strong evidence of abandonment despite a reasonably active initial release period.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month. This is not severe alone, but it provides no evidence of ongoing community or maintainer response.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, not a severe risk by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; the package's long inactivity makes this gap more relevant.