ollieread/multiauth
The MIT license, substantial README, repository tests, and changelog provide useful transparency. Workflow references are all unpinned and the project has no security policy, leaving avoidable maintenance and build-integrity gaps.
38%
Total Score
0
75
50
Health Score Breakdown
The latest registry release was in September 2014, nearly 12 years ago, with no releases in the last 12 months. That strongly raises abandonment and compatibility risk despite the package having 15 historical releases.
The repository recorded zero commits and zero active maintainers in the last 3 months. This provides no evidence of ongoing maintenance for a package whose registry release history is already very old.
The linked repository has no security policy. That is a transparency gap for a package handling authentication, though it is less serious than evidence of active security problems.
Both analyzed workflows completed the audit without findings or unsafe triggers, but all 8 action references are unpinned. This weakens build reproducibility and leaves dependency updates less controlled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ollie Read |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/auth Version ~4.1 | — | — |
illuminate/console Version ~4.1 | — | — |
illuminate/support Version ~4.1 | — | — |
illuminate/database Version ~4.1 | — | — |
illuminate/filesystem Version ~4.1 | — | — |
Weekly Downloads
Info
- Last Published
- 12 years ago
- Created
- 12 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.