Healthy and usable, with clear signs of active development and a complete source repository. The main caveats are that it is only 52 days old, all recent commits come from one contributor, and no security policy is present.
78%
Total Score
67
100
88
75
The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This supports package identity while offering no organizational maintenance redundancy.
One contributor made 100% of the 58 recent commits, leaving maintenance highly concentrated in a single person. The repository is active, but loss of that contributor would create meaningful continuity risk.
The repository uses Composer build tooling, but no security-scanning tools were detected. Build support is present, while automated security coverage is not evident.
The repository has no security policy. For an authentication and passkey UI package, the absence of a documented vulnerability-reporting path is a genuine transparency gap.
Version v0.32.0 is not a stable major release, but it is not marked as a prerelease and recent releases contain no prerelease versions. This is a modest maturity caveat rather than a major dependency risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/passkeys Version ^0.2.1 | — | — |
lattice-php/lattice Version >=0.77 <1.0 | — | — |
bambamboole/laravel-oidc-server Version 0.32.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.