The MIT license, focused dependency set, and clear README support adoption, but there is no security policy or automated security scanning. Its maintenance record remains the main concern for a package last released over four years ago.
38%
Total Score
25
100
78
83
The package has 35 releases but none in the last 12 months, and its latest release was over four years ago. That long gap materially raises abandonment risk.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push being over four years ago and indicating likely abandonment.
The package and repository are owned by the same individual account, so the ownership relationship is clear, but there is no organization backing shown to offset the single-owner maintenance risk.
The repository has no stars, forks, or watchers. This is weak supporting evidence rather than a verdict, but it offers no community signal to compensate for the inactivity.
Composer build tooling is present, but no security scanning tools were detected. For a small package this is a hygiene gap, though it is less serious than the maintenance inactivity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
lab404/laravel-impersonate Version ^1.7.3 | — | — |
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.