steroids/auth
The MIT license, matching repository, tests, and organization backing provide useful transparency. Missing security policy and scanning add avoidable risk for authentication software.
38%
Total Score
50
71
67
Health Score Breakdown
The package has had no releases in the last 12 months, and its latest release was published over four years ago. The earlier 52-release history shows past activity but does not offset the prolonged lapse.
There were no commits and no active maintainers in the last three months, consistent with the repository having been inactive for over four years. This is a substantial maintenance and abandonment concern.
Composer build tooling is present, but no security-scanning tools were detected. That leaves a meaningful assurance gap for an authentication package.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
The assessed release is still marked beta, and all recent releases are prereleases, so the public stability signal remains weak.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 steroids/core Version ^2.0@beta | — | — |
google/apiclient Version ^2.5 | — | — |
vkcom/vk-php-sdk Version ^5.101 | — | — |
pragmarx/google2fa Version ^8.0 | — | — |
bacon/bacon-qr-code Version ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 6 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.