The MIT license, matching repository, and straightforward Composer setup support basic transparency. Maintenance has stalled, documentation is extremely brief, and there are no repository tests or security scanning, making long-term adoption risky.
45%
Total Score
0
100
69
75
The latest release was published on December 25, 2024, and there have been no releases in the last 12 months. The four-release history shows an initially active project but no recent maintenance.
The repository recorded zero commits and zero active maintainers during the last 3 months, consistent with the long release gap and indicating likely abandonment risk.
The artifact includes a README, but it is only 54 characters and provides little integration guidance. The absence of tests and a changelog is normal for published artifacts and is not penalized here.
Composer build tooling is present, but no security scanning tools were detected. That weakens automated maintenance hygiene without proving a security defect.
The linked repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This adds a transparency gap for an authentication-related package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/sanctum Version ^4.0 | — | — |
laravel/framework Version ^11.20 | — | — |
thebachtiarz-company/laravel-base-v2 Version * | — | — |
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.