The MIT license, clear README, release notes, and repository tests provide useful transparency for integration. A single maintainer and missing security controls leave less evidence of durable project support.
68%
Total Score
50
100
89
83
Only one account has registry publishing access. That does not prove poor maintenance, but it leaves a thin publishing base and increases continuity risk.
The package and repository are owned by the same individual account, which is consistent ownership but does not provide organizational backing.
The repository recorded zero commits and zero active maintainers in the last three months, despite a recent release, so current maintenance activity is not demonstrated.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers external validation modestly rather than determining the verdict.
Composer is used for the build, but no security-scanning tools are configured, leaving automated detection coverage unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/workos Version ^0.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.