JavaScript client for client-personalization
88%
Total Score
healthy
Active Algolia-backed development and verified publishing outweigh the repository naming gap.
Eleven of 18 publishing accounts use the algolia.com domain, consistent with the organization-backed project. The personal-domain accounts vincentalindogan, eric-zaharia, fluf, sylvain, haroenv, tkrugg, and plnech are an account-hygiene caution, not evidence of weak maintenance capacity.
The repository name does not match the package and its README does not mention @algolia/client-personalization, creating some uncertainty about package-to-repository mapping. The package is nevertheless part of an organization-owned client repository, which partly reduces that concern.
No repository security policy was found, leaving vulnerability-reporting expectations less transparent. This is a documentation gap rather than evidence of abandonment, given the active organization-backed project.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@algolia/client-common Version 5.60.0 | — | — |
@algolia/requester-fetch Version 5.60.0 | — | — |
@algolia/requester-node-http Version 5.60.0 | — | — |
@algolia/requester-browser-xhr Version 5.60.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.