michaskruzelka/lacinka

Tests, documentation, licensing, and a small dependency surface make the package straightforward to adopt. The registry has seen no release since 2016, and the reported 1.0.0 differs from the latest listed 0.1.3. The repository is not archived and was pushed in 2024.

Latest 1.0.0

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has four releases, but none in the last 12 months and its latest release was in 2016. This long registry gap is a meaningful maintenance concern despite the repository having a later push.

Repo commit activity

There were no commits or active maintainers in the preceding three months, indicating currently limited development activity. The 2024 push provides some compensating evidence but does not remove the caution.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest repository hygiene gap rather than a severe dependency risk.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and response. This is a minor concern for a small library, not evidence of unsafe code.

Version stability

The assessed version is 1.0.0 while the registry reports 0.1.3 as the latest version, creating release metadata inconsistency that warrants checking before adoption.