laikait/laika-cache

Usable with caveats: the release is clearly packaged, tested, licensed, and backed by a matching repository, but it is newly published with no established maintenance record. The repository also lacks a security policy and explicit workflow permissions, so adoption should wait for more project history if this is a critical dependency.

Latest v1.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's first release and it was published less than 1 hour ago, so there is no demonstrated release cadence or long-term maintenance history. The repository's tests and release automation provide some early evidence of project activity.

Repo commit activity

There were no commits or active maintainers during the last 3 months, but the repository is newly created and was pushed about 1 hour ago. This remains insufficient evidence of sustained maintenance rather than evidence of abandonment.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The limited tooling is acceptable for a small new package, though it leaves security and maintenance checks less transparent.

Security policy

The repository has no security policy. That is a transparency gap for reporting vulnerabilities, although the package's small scope and included tests provide some compensating project hygiene.

Token permissions

The only workflow lacks top-level permissions and uses job-level permissions without declaring read-only permissions. No write permissions were found, but explicit least-privilege settings would make the CI configuration safer and clearer.