The README, tests, MIT license, and small dependency surface support straightforward integration. There is no security policy or repository security scanning, so maintenance assurance remains limited.
68%
Total Score
50
100
79
75
The repository is owned by an individual user rather than an organization, so the small project footprint is not offset by visible organizational backing.
The package is only 0 days old with two releases, and the median interval is about 28 minutes. That shows active initial publishing but provides no meaningful long-term maintenance history.
No commits or active maintainers were recorded in the prior three months. Because the repository was also pushed on the assessment day, this is evidence of very limited history rather than clear abandonment.
Composer build tooling is present, but no repository security scanning tools were detected. That is a modest transparency and maintenance gap, not a severe dependency risk by itself.
The repository has no security policy. For a package integrating Laravel and a browser-facing editor, this leaves vulnerability-reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
No direct dependencies.
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.