baywa-re-lusy/laminas-api-problem

Licensedanger

The manifest declares a proprietary license and no license file was found. That creates a material transparency and reuse concern for an open-source dependency.

Release historydanger

The package has had no releases in more than four years, with only three releases overall and none in the last 12 months. This is strong evidence of abandonment risk despite the repository remaining available.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. This materially increases abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This lowers transparency, although it is less severe than the maintenance and licensing concerns.