Mem0 API for Laravel
57%
Total Score
caution
Usable with caveats: the latest release is about ten months old and the repository has had no commits in three months.
A post-autoload-dump install script is present. This is a modest supply-chain and installation-complexity consideration, but the signal does not show that the script is unsafe.
Only one account has registry publishing access. The repository is user-owned rather than organization-owned, so there is limited visible publishing redundancy.
The package has 9 releases over about 13 months, but only 2 releases in the last year and the latest was about ten months ago, indicating a slowing release cadence.
The repository recorded no commits and no active maintainers in the last three months, which is meaningful evidence of stalled maintenance for an API integration package.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a transparency and hygiene gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.9.0 | — | — |
spatie/laravel-data Version ^4.13 | — | — |
illuminate/contracts Version ^10.0||^11.0||^12.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.