ydg/monolog-aliyun-log

Release historydanger

Only two releases were published, with no release in over three years. That strongly limits evidence of ongoing maintenance for a logging integration.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the repository having been inactive for over three years. This raises abandonment risk.

Repo popularitycaution

The repository has one star and no forks, providing little evidence of broad community use or external review. This is supporting caution rather than a verdict by itself.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. The missing scanning is a hygiene weakness, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters more for a package that connects application logging to an external service.