Tests, documentation, and licensing provide a solid foundation for integration. The small user base and limited recent activity make long-term support less certain.
68%
Total Score
50
88
50
The package has 12 releases over about five and a half years, but it has had no releases in the last 12 months and its latest release was about 19 months ago. This raises maintenance uncertainty despite a previously established release history.
There were zero commits and zero active maintainers in the last three months, which weakens evidence of active maintenance. The repository's more recent push prevents treating the project as abandoned outright.
The repository has 3 stars, 2 forks, and 1 watcher, indicating a small adoption base. This is supporting caution about maintenance capacity, not a verdict by itself.
No security policy is present in the repository, leaving vulnerability-reporting expectations unclear. This is a hygiene concern rather than evidence that the release is unsafe.
The single workflow was fully analyzed with no detected dangerous sinks or audit findings, but all 8 of 8 action references are unpinned. That leaves avoidable dependency-integrity risk in the build workflow.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/sanctum Version ^v4.0 | — | — |
laravel-doctrine/orm Version ^3.0.0 | — | — |
ramsey/uuid-doctrine Version ^2.0.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.