The repository has had no commits in the last three months and was last pushed over three years ago. MIT licensing, release notes, security scanning, and readme coverage improve transparency, but the long release gap remains a substantial adoption risk.
42%
Total Score
25
100
81
67
The package has made 17 releases, but none in the last 12 months; its latest release was over four years ago. This extended release gap materially raises abandonment and compatibility risk.
There were no commits and no active maintainers in the last three months. Combined with the old last push, this is strong evidence that maintenance has stalled.
The registry namespace and repository are owned by the same individual account, providing direct ownership alignment but no evidence of organizational backing or broader maintenance capacity.
The linked repository is not archived, but it was last pushed over three years ago, so its unarchived status does not compensate for the observed inactivity.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for an authentication package. This is a transparency gap that matters to consumers.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
aws/aws-sdk-php Version >=3.0 | — | — |
guzzlehttp/guzzle Version ^6.0|^7.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.