Flare error tracker integration for Craft CMS
78%
Total Score
80
100
89
80
All recent commits come from one contributor, creating a concentrated maintenance risk. Organization ownership provides some handoff capacity, but no second active contributor is shown in this signal.
Only one commit was recorded in the last 3 months from one active maintainer. Recent release activity and a repository push are compensating evidence, but the low current commit volume still warrants caution about maintenance capacity.
The repository has zero stars and forks and one watcher. This provides little external validation, but popularity is supporting evidence only and does not outweigh the package's release and ownership signals.
The repository uses Composer build tooling, but no security scanning tools were detected. The build setup is healthy, while the absent scanning is a modest transparency and assurance gap.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a hygiene gap, not evidence that the package is unsafe to depend on.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.0 | — | — |
spatie/flare-client-php Version ^2.10 | — | — |
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.