msp/security-suite

Release historydanger

The package has had no release in over eight years, despite 36 releases historically; this strongly indicates abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push being over seven years ago; this is strong evidence of stalled maintenance.

Dependency profilecaution

Seven runtime dependencies are expected for a metapackage bundling multiple security modules, but they also enlarge the set of components whose maintenance must be trusted.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a security-focused suite, that is a transparency and maintenance weakness.

Security policycaution

The linked repository has no security policy, leaving no documented path for reporting vulnerabilities in a security-focused package.