The package includes a clear README, exact-version release notes, and a focused dependency set. Its small project has no recent commits or security scanning, so ongoing maintenance and oversight remain uncertain.
55%
Total Score
50
88
83
This is the sole release, published 448 days ago, with no releases in the last 12 months. That leaves little evidence of sustained maintenance for a package handling authentication.
There were no commits or active maintainers in the last three months, which is meaningful for a package with only one release and raises abandonment risk.
Composer build tooling is present, but no security scanning tooling was detected. The missing scanning is a modest transparency and maintenance concern rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented reporting or response process for an authentication package. This is a real but limited transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tempest/auth Version ^1.0 | — | — |
tempest/core Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
tempest/framework Version ^1.0 | — | — |
league/oauth2-client Version ^2.6 | — | — |
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.