Sanctum use cache to retrieve token
58%
Total Score
caution
Usable with caveats: no commits for 18 months and only one maintainer.
Only one registry maintainer is listed, and the project is backed by a personal repository rather than an organization. That creates limited continuity if the maintainer becomes unavailable.
The latest release was about 18 months ago, with no releases in the last 12 months. This suggests slowing maintenance, although the package has four releases and is not deprecated.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. This raises abandonment risk for a package integrated into authentication-related request handling.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap for a package that changes token retrieval behavior.
The repository has no security policy. That leaves vulnerability-reporting and response expectations unclear, though the absence is not evidence of a vulnerability.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/sanctum Version ^2.0|^3.0|^4.0 | — | — |
illuminate/cache Version ^8.0|^9.0|^10.0|^11.0|^12.0 | — | — |
laravel/framework Version ~8.0|~9.0|~10.0|~11.0|~12.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.