laiz/laiz-session

Risky to adopt: the last release and repository activity were about 12 years ago, with no recent maintenance evidence. The package is not deprecated or archived and has a declared MIT license, but its missing README and minimal project hygiene increase the cost of relying on it.

Latest v0.1.2

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only three releases exist, with none in the last 12 months, and the latest release was published about 12 years ago. This is strong evidence of abandonment for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long period without releases. No provided signal compensates for this lack of current maintenance.

Package scaffolding

The published artifact has no README, which is a meaningful transparency and integration gap for a library; absent tests and changelog files in the package are normal packaging practice and do not add concern.

Repo popularity

The repository has zero stars and forks and only one watcher. This provides little external evidence of adoption or community support, but popularity is supporting evidence rather than a verdict.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tool is configured. This is a minor hygiene gap in an otherwise very old repository.