The project has had no commits or active maintainers in the last three months, and it has only published one release in about ten months. MIT licensing, tests, release notes, and organization ownership provide useful transparency and continuity.
63%
Total Score
75
100
79
75
The package has only one release, with no follow-up releases across about ten months. That leaves maintenance continuity unproven for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the single-release history, this is a meaningful maintenance concern.
The repository has no stars, forks, or watchers. This is weak supporting evidence rather than a verdict, but it provides no external adoption signal to offset the quiet maintenance record.
Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap, not evidence that the package is unsafe.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^12.0 | — | — |
spatie/simple-excel Version ^3.7 | — | — |
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.