Tests, a README, and an MIT declaration provide useful basics for consumers. The package has had no release or repository activity for nearly three years, and it lacks a security policy.
45%
Total Score
50
100
81
50
The package has released nothing in the last 12 months, and its latest release was about 2 years and 9 months ago. Earlier release activity shows a real project history, but the prolonged current gap lowers confidence in ongoing maintenance.
There were zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating that maintenance has effectively stopped.
The package defines four Composer lifecycle scripts, including post-create-project and post-update hooks. These can execute during installation or updates, creating extra consumer exposure even though lifecycle scripts are common in framework packages.
Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a transparency and hygiene concern, not evidence that the package is unsafe.
The repository has no security policy. For a framework package handling application authentication and request flows, that reduces transparency around vulnerability reporting and maintenance response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cyberbugz/dust Version ^v5.0 | — | — |
laravel/tinker Version ^2.8 | — | — |
laravel/sanctum Version ^3.2 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
laravel/framework Version ^10.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.