Usable with caveats: the release is current, documented, tested, licensed, and backed by a matching organization repository. However, only two releases exist across nearly two years and there were no commits in the last three months, so ongoing maintenance capacity is uncertain.
68%
Total Score
83
50
88
90
The package has 10 runtime dependencies, including several related tomatophp packages and framework components. This is a meaningful integration surface, though the dependencies are consistent with the package's documented Filament blog functionality.
Only two releases have been published over roughly 1 year 11 months, with one release in the last 12 months. The long release interval makes ongoing maintenance less certain, despite the recent release.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the sparse release history, this is the main evidence of uncertain ongoing maintenance.
Composer build tooling is present, but no security scanning tool was detected. The missing scanner is a hygiene gap, although it is not by itself evidence that the package is unsafe.
The single workflow does not declare top-level token permissions. No write-enabled permissions were detected, but explicit least-privilege declarations would provide stronger workflow transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^5.0 | — | — |
tomatophp/filament-cms Version ^5.0 | — | — |
tomatophp/filament-seo Version ^5.0 | — | — |
spatie/laravel-markdown Version ^2.8 | — | — |
tomatophp/filament-menus Version ^5.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.