simsoft/slim

This release appears usable and reasonably transparent: it is licensed, documented, tested, version-stable, non-deprecated, backed by a matching repository, and has a substantial source tree with changelog and security policy coverage. However, maintenance capacity is a concern because the repository recorded zero commits and zero active maintainers in the last 3 months, while registry publishing is controlled by one maintainer and repository popularity is minimal. Recent releases and two merged pull requests provide some compensating evidence, so this is a cautionary dependency rather than an obviously unfit one; verify continued maintenance before making it foundational.

Latest 3.0.0

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one registry account has publish access, which creates a limited publishing succession path. The repository's recent merged pull requests provide some activity evidence, but registry access itself does not establish a broader maintenance base.

Project backing

The repository is owned by a user account rather than an organization, so there is no demonstrated organizational backing to compensate for the thin maintainer base.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers over the last 3 months, a meaningful maintenance concern. Recent publication and merged pull requests show some activity but do not remove the risk of a recent slowdown.

Repo popularity

The repository has 0 stars and 0 forks, with only 2 watchers. Popularity is supporting evidence rather than a verdict, but these values provide little external validation or community resilience.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The repository's SECURITY.md and read-only workflow permissions provide compensating hygiene, though automated security coverage remains limited.