Usable with caveats: the release is licensed, clearly documented, tested, and backed by a matching non-archived repository. However, the repository has had no commits in four months and its workflow does not declare top-level token permissions, so verify that maintenance resumes before relying on it heavily.
69%
Total Score
50
100
94
67
The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the limited recent activity.
This is a young package, about 5 months old, with three releases and a median interval of about 14 days. That shows an initial release cadence, though the short history limits confidence in long-term maintenance.
The repository recorded zero commits and zero active maintainers over the last three months, leaving no evidence of ongoing maintenance after the current release and creating a meaningful abandonment concern.
No repository security policy is present, which makes vulnerability reporting and disclosure expectations less transparent for a package handling email-monitoring data.
The only workflow lacks top-level token permissions. No write-enabled workflow was observed, but explicitly restricting permissions would provide stronger CI safety guarantees.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^12.0|^13.0 | — | — |
filament/filament Version ^5.0 | — | — |
livewire/livewire Version ^4.0 | — | — |
illuminate/console Version ^12.0|^13.0 | — | — |
illuminate/support Version ^12.0|^13.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.