leafs/auth
The package has a five-year history, a documented release, tests, and a healthy two-person maintenance base. Its small popularity and absent security policy limit confidence, while workflow hygiene needs attention.
86%
Total Score
88
94
83
Health Score Breakdown
There are no open issues and nine new pull requests in the last month, although none were merged during that period. This is worth monitoring but is not enough to outweigh the recent commit activity.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and assurance gap for an authentication package.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented for a security-sensitive authentication library.
Both workflows were fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all four action references are unpinned, weakening build reproducibility and supply-chain hygiene.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Michael Darko |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 leafs/db Version ^5.0 | — | — |
leafs/date Version ^5.0 | — | — |
leafs/http Version ^5.0 | — | — |
leafs/session Version ^5.0 | — | — |
leafs/password Version ^5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 5 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.