The project has had no commits or releases for over six years, and its repository has no security policy or scanning tools. A README, tests, release notes, MIT declaration, and non-archived repository provide useful transparency but do not offset the abandonment risk.
40%
Total Score
0
63
50
The latest release was over six years ago, with no releases in the last 12 months. Seven releases show some initial activity, but the long period of inactivity materially raises abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the release history showing prolonged inactivity. This is the strongest evidence of abandonment risk.
The package defines post-autoload-dump, post-create-project-cmd, and post-root-package-install scripts. These add install-time behavior that should be reviewed, but they are not by themselves evidence of poor maintenance.
The repository has zero stars and forks and only one watcher. Popularity is not decisive by itself, but these figures provide no supporting evidence of adoption or an active community.
Composer is used for the build, but no security scanning tools are present. The missing scanning is a hygiene gap, though it is less significant than the prolonged inactivity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version ^1.0 | — | — |
fideloper/proxy Version ^4.0 | — | — |
google/recaptcha Version ^1.2 | — | — |
artesaos/seotools Version ^0.16.0 | — | — |
laravel/framework Version ^6.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.