@algolia/cache-common No license 63 versions

@algolia/cache-common

npm Repository

63

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): eric-zaharia has 213 approved packages in the Algolia ecosystem; publisher change reflects an internal Algolia maintainer transition, not a hostile takeover.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer eric-zaharia is an established Algolia publisher with a strong approval track record across the same package ecosystem.	ai	2026/04/24

Versions (showing 63 of 63)

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.25.1

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.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

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.23.3

1 finding

LOW No provenance attestation provenance

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

v4.23.2

1 finding

LOW No provenance attestation provenance

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

v4.23.1

1 finding

LOW No provenance attestation provenance

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

v4.23.0

1 finding

LOW No provenance attestation provenance

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

v4.22.1

1 finding

LOW No provenance attestation provenance

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

v4.22.0

1 finding

LOW No provenance attestation provenance

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

v4.21.1

1 finding

LOW No provenance attestation provenance

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

v4.21.0

1 finding

LOW No provenance attestation provenance

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

v4.20.0

1 finding

LOW No provenance attestation provenance

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

v4.19.1

1 finding

LOW No provenance attestation provenance

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

v4.19.0

1 finding

LOW No provenance attestation provenance

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

v4.18.0

1 finding

LOW No provenance attestation provenance

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

v4.17.2

1 finding

LOW No provenance attestation provenance

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

v4.17.1

1 finding

LOW No provenance attestation provenance

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

v4.17.0

1 finding

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

LOW No provenance attestation provenance

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

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

[Accepted risk] 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.

v4.15.0

2 findings

LOW No provenance attestation provenance

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

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

[Accepted risk] 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.

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.

v4.6.0

1 finding

LOW No provenance attestation provenance

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

v4.5.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yannickcr → haroenv (on 2020-09-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-09-14. This could indicate a legitimate maintainer transition or an account compromise.

v4.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yannickcr → haroenv (on 2020-09-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-09-14. This could indicate a legitimate maintainer transition or an account compromise.

v4.4.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yannickcr → haroenv (on 2020-08-06) provenance

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

v4.3.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yannickcr → haroenv (on 2020-07-20) provenance

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

v4.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: nunomaduro → yannickcr (on 2020-06-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-11. This could indicate a legitimate maintainer transition or an account compromise.

v4.2.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: nunomaduro → haroenv (on 2020-04-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-21. This could indicate a legitimate maintainer transition or an account compromise.

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

1 finding

LOW No provenance attestation provenance

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

v4.0.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.