contao-monitoring/monitoring-scan-client

Release historydanger

The latest release was published in February 2018, with no releases in the last 12 months. This long period without a registry release creates a substantial abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Although the repository is not archived, there is no recent development evidence to compensate for the stale release history.

Maintainerscaution

Only one account has registry publish access, which is a narrow publishing base. The organization-owned repository provides some compensating project backing, so this is not a severe concern by itself.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tools were detected. This is a modest repository hygiene gap rather than evidence that the release is unsafe to depend on.

Security policycaution

The repository has no published security policy. That reduces transparency for reporting and handling vulnerabilities, though it does not independently establish abandonment.