The package is clearly identified, MIT-licensed, and has a small, understandable file tree with no install-time scripts. Its five runtime dependencies and lack of security tooling add some ongoing maintenance burden for a Laravel integration.
38%
Total Score
0
75
83
The package has had no release in over six years: its latest release was published in May 2020, with three releases total and none in the last 12 months. This is strong evidence of abandonment for a dependency that must track Laravel and registry changes.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no recent maintenance. No provided signal compensates for this prolonged inactivity.
The repository has only 3 stars, 0 forks, and 1 watcher, providing little evidence of a broad user or contributor base. Popularity is supporting evidence rather than decisive, but this increases abandonment concern alongside the inactive repository.
Composer is used for builds, which fits the package, but no security scanning tools are present. This is a modest transparency and maintenance gap rather than a standalone severe risk.
The repository has no security policy. For a small command-line Laravel package this is a transparency gap, though it is less significant than the absence of recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/semver Version ^1.0 | — | — |
illuminate/support Version >=6.0 | — | — |
knplabs/packagist-api Version ^1.5 | — | — |
paquettg/php-html-parser Version ^2.1 | — | — |
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.