opportus/sls-client

The documented roadmap still lists core features, validation, tests, and benchmarks as unfinished, and the project has no security policy. The MIT license, README, and repository tests provide useful transparency, but do not offset the maintenance risk.

Latest v1.0.0-alpha.1

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, first published about 6 years and 9 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with the repository's last push being about 6 years and 9 months ago. This materially increases abandonment risk.

Package scaffolding

The package includes a README and the repository has tests, but the README explicitly lists cache support, unit and functional tests, benchmarks, all SLS methods, and request validation as unfinished. The GitHub release confirms release transparency for this version, but not implementation completeness.

Repo tooling

The repository uses Composer, which supports reproducible project builds, but it has no security scanning tools. That is a maintenance and transparency gap for a package handling service requests.

Security policy

No security policy was found in the linked repository. This weakens the project's disclosure and response process, although it is not by itself evidence of unsafe code.