msp/antivirus

Release historydanger

The package has had no release in more than 8 years: its latest release was October 29, 2017, despite eight releases overall. This is strong evidence that compatibility and defect fixes are no longer being maintained.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months, consistent with the repository having stopped after October 2017. For a security-related integration, this materially increases abandonment and compatibility risk.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, with one issue still open. This reinforces the lack of recent project activity rather than showing active support.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a meaningful hygiene gap for a module intended to inspect potentially malicious uploads.

Security policycaution

The repository has no security policy. For a security-sensitive package, the absence of a documented vulnerability-reporting path lowers transparency and response confidence.