mfrost503/snaggle

It has clear documentation, tests, a changelog, and a small runtime dependency surface. The source repository is not archived, but its lack of recent activity leaves compatibility and maintenance uncertain.

Latest 1.0.1

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest registry release was over 7 years ago, with no releases in the last 12 months. That long release gap is a substantial maintenance and compatibility concern despite six historical releases.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the old last push, this indicates effectively dormant project maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a dormant library this is a modest transparency and maintenance gap, not a severe risk by itself.

Repository archived

The repository is not archived, which avoids an abandonment verdict, but it was last pushed over 11 years ago. The non-archived status does not compensate for that inactivity.

Security policy

The repository has no security policy. That leaves vulnerability reporting and response expectations undocumented, which matters for an OAuth client library.