Here you can create a todo list of your tasks. And you can close and delete tasks from the list
43%
Total Score
unhealthy
A single release has had no follow-up or recent commits for about two years, with limited security transparency and a repository mismatch.
This is the package's only release, published about two years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a package intended as a dependency.
The repository had zero commits and zero active maintainers in the last three months, while its last push was about two years ago. This confirms that the old release is not being actively maintained.
The registry namespace and repository owner are individual accounts rather than an organization, so the one-person publishing base is not explained by organization backing. This matters alongside the lack of recent activity.
There were no new or closed issues or pull requests in the last month. Combined with zero recent commits, this suggests little current project activity rather than merely a quiet release cycle.
The linked repository name does not match the package name, and the README mention could not be determined. A mismatch can indicate that the package is hosted in an unrelated or reused repository, reducing transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^2.8 | — | — |
laravel/sanctum Version ^3.3 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
laravel/framework Version ^10.10 | — | — |
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.