Tinker on vscode
67%
Total Score
50
86
75
The package has only two releases over about one year, with one release in the last 12 months and a median interval of about 341 days. This is limited maintenance evidence, though it does not show clear abandonment by itself.
There were no commits and no active maintainers in the last three months. Although the latest release was recent, the lack of recent commit activity weakens evidence of ongoing maintenance.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest transparency and hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. This limits disclosure guidance and project transparency, but it is not by itself evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/tinker Version * | — | — |
illuminate/http Version * | — | — |
symfony/console Version * | — | — |
react/event-loop Version ^1.2 | — | — |
illuminate/console 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.