@algolia/client-recommendation No license 51 versions

@algolia/client-recommendation

npm Repository

51

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

haroenvshortcutseric-zahariafluf

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change reflects legitimate Algolia team transition; haroenv is a long-standing trusted contributor with 1412 approved packages.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are consistent with normal team evolution at Algolia; no hostile takeover indicators.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Maintainer removals reflect normal team rotation at Algolia; no malicious indicators.	ai	2026/04/24
npm-metadata	no-description	AI (npm-metadata): Algolia's scoped client packages in this monorepo consistently lack descriptions; this is a known pattern, not a malicious signal.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Algolia's JS client packages have not historically used Sigstore provenance; absence is consistent across the package family.	ai	2026/04/24

Versions (showing 51 of 63)

View all versions

Version	Deps	Published
4.27.0	3 / 0	2026-02-27
4.26.0	3 / 0	2026-02-17
4.25.3	3 / 0	2025-11-06
4.25.2	3 / 0	2025-06-23
4.25.1	3 / 0	2025-06-23
4.25.0	3 / 0	2025-06-19
4.24.0	3 / 0	2024-06-25
4.23.3	3 / 0	2024-04-10
4.23.2	3 / 0	2024-03-27
4.23.1	3 / 0	2024-03-26
4.23.0	3 / 0	2024-03-26
4.22.1	3 / 0	2024-01-09
4.22.0	3 / 0	2023-12-14
4.21.1	3 / 0	2023-12-12
4.21.0	3 / 0	2023-12-11
4.20.0	3 / 0	2023-09-12
4.19.1	3 / 0	2023-07-20
4.19.0	3 / 0	2023-07-18
4.18.0	3 / 0	2023-06-23
4.17.2	3 / 0	2023-06-08
4.17.1	3 / 0	2023-05-24
4.17.0	3 / 0	2023-04-03
4.16.0	3 / 0	2023-03-23
4.15.0	3 / 0	2023-03-02
4.14.3	3 / 0	2022-12-19
4.14.2	3 / 0	2022-07-27
4.14.1	3 / 0	2022-07-20
4.14.0	3 / 0	2022-07-18
4.13.1	3 / 0	2022-05-18
4.13.0	3 / 0	2022-03-14
4.12.2	3 / 0	2022-03-02
4.12.1	3 / 0	2022-01-28
4.12.0	3 / 0	2022-01-07
4.11.0	3 / 0	2021-10-20
4.10.5	3 / 0	2021-08-26
4.10.4	3 / 0	2021-08-23
4.10.3	3 / 0	2021-07-05
4.10.2	3 / 0	2021-06-23
4.10.0	3 / 0	2021-06-23
4.9.3	3 / 0	2021-06-15
4.9.2	3 / 0	2021-06-10
4.9.1	3 / 0	2021-04-26
4.9.0	3 / 0	2021-04-13
4.8.6	3 / 0	2021-03-08
4.8.5	3 / 0	2021-02-08
4.8.4	3 / 0	2021-01-20
4.8.3	3 / 0	2020-12-03
4.8.2	3 / 0	2020-11-26
4.8.1	3 / 0	2020-11-25
4.8.0	3 / 0	2020-11-19
4.7.0	3 / 0	2020-11-16

v4.27.0

2 findings

HIGH Publisher changed: fluf → eric-zaharia (on 2026-02-27) provenance

This version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.25.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.25.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.25.1

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2025-06-23) provenance

This version was published by a different npm account than previous versions on 2025-06-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.24.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2024-06-25) provenance

This version was published by a different npm account than previous versions on 2024-06-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.23.3

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2024-04-10) provenance

This version was published by a different npm account than previous versions on 2024-04-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.23.2

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2024-03-27) provenance

This version was published by a different npm account than previous versions on 2024-03-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.23.1

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2024-03-26) provenance

This version was published by a different npm account than previous versions on 2024-03-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.23.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2024-03-26) provenance

This version was published by a different npm account than previous versions on 2024-03-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.22.1

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2024-01-09) provenance

This version was published by a different npm account than previous versions on 2024-01-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.22.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-12-14) provenance

This version was published by a different npm account than previous versions on 2023-12-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.21.1

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-12-12) provenance

This version was published by a different npm account than previous versions on 2023-12-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.21.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-12-11) provenance

This version was published by a different npm account than previous versions on 2023-12-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.20.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-09-12) provenance

This version was published by a different npm account than previous versions on 2023-09-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.19.1

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-07-20) provenance

This version was published by a different npm account than previous versions on 2023-07-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.19.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-07-18) provenance

This version was published by a different npm account than previous versions on 2023-07-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.18.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-06-23) provenance

This version was published by a different npm account than previous versions on 2023-06-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.17.2

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-06-08) provenance

This version was published by a different npm account than previous versions on 2023-06-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.17.1

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-05-24) provenance

This version was published by a different npm account than previous versions on 2023-05-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.17.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-04-03) provenance

This version was published by a different npm account than previous versions on 2023-04-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.16.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-03-23) provenance

This version was published by a different npm account than previous versions on 2023-03-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.15.0

2 findings

HIGH Publisher changed: haroenv → shortcuts (on 2023-03-02) provenance

This version was published by a different npm account than previous versions on 2023-03-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.14.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.14.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.10.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.10.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.9.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.