kzu/security

Release historydanger

Only two releases exist, with the latest published in March 2023 and no releases in the last 12 months. The long release gap is meaningful abandonment risk for a dependency.

Repo commit activitydanger

There were no commits or active maintainers in the last three months, consistent with the release gap and providing weak evidence of ongoing maintenance.

Package file treecaution

The package contains only five files, including one source file and its Composer metadata. This is transparent and easy to inspect, although it also provides little evidence of broader project maturity.

Package scaffoldingcaution

The artifact has no README, tests, or changelog. Missing tests and changelog are normal for published packages, but the missing README reduces transparency for a library consumers must integrate.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no provided organizational backing to compensate for the thin maintenance record.