zenky/ui

Licensedanger

The manifest declares the package proprietary, with no detected license and no license file in either the artifact or repository. That creates a serious licensing barrier for an open-source dependency.

Release historycaution

This is the first recorded release, published today, so there is no demonstrated release cadence or track record yet. The linked repository is also newly created, which explains the limited history but does not remove the uncertainty.

Repo commit activitycaution

The repository has zero commits in the last three months and zero active maintainers in that period. Because the project is newly released, this is partly explained by its age, but sustained maintenance is not yet demonstrated.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. This is a maintenance and transparency gap rather than evidence of unsafe code.

Security policycaution

The repository has no security policy. That leaves vulnerability reporting and response expectations undocumented for consumers.