Usable with caveats: the repository is active enough to be identifiable and the release has no install-time scripts, but it has only one release and no commits in the last three months. Zero repository adoption, no repository tests, and missing security controls make long-term maintenance uncertain.
52%
Total Score
50
50
75
80
There were no commits and no active maintainers in the last three months. Combined with the single-release history, this is the clearest sign that maintenance may have stalled.
The package declares eight runtime dependencies, including framework, testing, archive, and rendering components. This is a meaningful integration surface and increases maintenance burden, though it is not inherently unsafe.
The manifest declares a proprietary license, while the repository contains a license file. The repository file means licensing evidence exists, but the proprietary declaration may impose restrictions that developers should verify before adoption.
This is the package's only release, published about 405 days ago, with no releases in the last 12 months. That provides little evidence of sustained maintenance or compatibility work.
There are no open issues or pull requests and no issue or pull-request activity in the last month. This is neutral for a small package but offers no evidence of an active user or maintainer community.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pestphp/pest Version ^2.36 | — | — |
illuminate/config Version v10|v11|v12 | — | — |
illuminate/support Version v10|v11|v12 | — | — |
illuminate/database Version v10|v11|v12 | — | — |
barryvdh/laravel-snappy Version ^1.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.