algoliasearch
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@algolia/client-recommendation | AI (dependencies): First-party @algolia scoped package, part of the same coordinated monorepo release at matching version 4.0.0. No independent risk. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in this package is used for parsing Algolia secured API keys — a documented, legitimate feature with no malicious payload risk. | ai | |
| provenance | missing-githead | AI (provenance): Diff baseline is v5.x; v4.x maintenance releases have different build/publish tooling. Not indicative of compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All added deps are @algolia/* at matching version — standard v4.x dependency tree. Diff misleading due to v5.x baseline. | ai | |
| phantom-deps | phantom-dep:@algolia/requester-browser-xhr | AI (phantom-deps): Same as above — v4 sub-package architecture uses indirect bundled references rather than direct imports. | ai | |
| phantom-deps | phantom-dep:@algolia/cache-browser-local-storage | AI (phantom-deps): algoliasearch v4 bundles sub-packages into dist files; indirect usage via bundle is the documented architecture for this package family. | ai | |
| phantom-deps | phantom-dep:@algolia/logger-console | AI (phantom-deps): Same as above — v4 sub-package architecture uses indirect bundled references rather than direct imports. | ai | |
| phantom-deps | phantom-dep:@algolia/client-account | AI (phantom-deps): Same as above — v4 sub-package architecture uses indirect bundled references rather than direct imports. | ai | |
| provenance | publisher-changed | AI (provenance): Algolia migrated to GitHub Actions CI/CD publishing, corroborated by SLSA provenance attestation. This is a legitimate organizational change for this major company's package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer 'fluf' is consistent with internal Algolia team management for this established, company-owned package. | ai | |
| dependencies | unvetted-dep:@algolia/requester-node-http | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/requester-browser-xhr | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/abtesting | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/client-query-suggestions | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| phantom-deps | phantom-dep:@algolia/requester-fetch | AI (phantom-deps): Declared as a dependency and referenced in config files; consistent with bundling setup in this monorepo package. Not a true phantom dependency. | ai | |
| dependencies | unvetted-dep:@algolia/client-personalization | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/ingestion | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/recommend | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/monitoring | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/client-common | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/client-search | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/client-insights | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/requester-fetch | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/client-abtesting | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai | |
| dependencies | unvetted-dep:@algolia/client-analytics | AI (dependencies): First-party Algolia monorepo sub-package, always released in lockstep with algoliasearch. Not a third-party dependency. | ai |
Versions (showing 100 of 159)
| Version | Deps | Published |
|---|---|---|
| 5.53.0 | 14 / 11 | |
| 5.52.1 | 14 / 11 | |
| 5.52.0 | 14 / 11 | |
| 5.51.0 | 14 / 11 | |
| 5.50.2 | 14 / 11 | |
| 5.50.1 | 14 / 11 | |
| 5.50.0 | 14 / 11 | |
| 5.49.2 | 14 / 11 | |
| 5.49.1 | 14 / 11 | |
| 5.49.0 | 14 / 11 | |
| 5.48.2 | 14 / 11 | |
| 5.48.1 | 14 / 11 | |
| 5.48.0 | 14 / 11 | |
| 5.47.0 | 14 / 11 | |
| 5.46.4 | 14 / 11 | |
| 5.46.3 | 14 / 11 | |
| 5.46.2 | 14 / 11 | |
| 5.46.1 | 14 / 11 | |
| 5.46.0 | 14 / 11 | |
| 5.45.0 | 14 / 11 | |
| 5.44.0 | 14 / 11 | |
| 5.43.0 | 14 / 11 | |
| 5.42.0 | 14 / 11 | |
| 5.41.0 | 14 / 11 | |
| 5.40.1 | 14 / 11 | |
| 5.40.0 | 14 / 11 | |
| 5.39.0 | 14 / 11 | |
| 5.38.0 | 14 / 11 | |
| 5.37.0 | 14 / 11 | |
| 5.36.0 | 14 / 11 | |
| 5.35.0 | 14 / 11 | |
| 5.34.1 | 13 / 11 | |
| 5.34.0 | 13 / 11 | |
| 5.33.0 | 13 / 11 | |
| 5.32.0 | 13 / 11 | |
| 5.31.0 | 13 / 11 | |
| 5.30.0 | 13 / 11 | |
| 5.29.0 | 13 / 11 | |
| 5.28.0 | 13 / 11 | |
| 5.27.0 | 13 / 11 | |
| 5.26.0 | 13 / 11 | |
| 5.25.0 | 13 / 11 | |
| 5.24.0 | 13 / 11 | |
| 5.23.4 | 13 / 11 | |
| 5.23.3 | 13 / 11 | |
| 5.23.2 | 13 / 10 | |
| 5.23.1 | 13 / 10 | |
| 5.23.0 | 13 / 10 | |
| 5.22.0 | 13 / 10 | |
| 5.21.0 | 13 / 10 | |
| 5.20.4 | 13 / 10 | |
| 5.20.3 | 13 / 10 | |
| 5.20.2 | 13 / 10 | |
| 5.20.1 | 13 / 10 | |
| 5.20.0 | 13 / 10 | |
| 5.19.0 | 13 / 10 | |
| 5.18.0 | 13 / 10 | |
| 5.17.1 | 13 / 10 | |
| 5.17.0 | 13 / 10 | |
| 5.16.0 | 13 / 10 | |
| 5.15.0 | 13 / 10 | |
| 5.14.2 | 13 / 10 | |
| 5.14.1 | 13 / 10 | |
| 5.14.0 | 13 / 10 | |
| 5.13.0 | 13 / 10 | |
| 5.12.0 | 13 / 10 | |
| 5.11.0 | 13 / 10 | |
| 5.10.2 | 13 / 10 | |
| 5.10.1 | 13 / 10 | |
| 5.10.0 | 13 / 10 | |
| 5.9.1 | 13 / 10 | |
| 5.9.0 | 12 / 10 | |
| 5.8.1 | 9 / 10 | |
| 5.8.0 | 9 / 10 | |
| 5.7.0 | 9 / 10 | |
| 5.6.1 | 9 / 10 | |
| 5.6.0 | 9 / 10 | |
| 5.5.3 | 9 / 10 | |
| 5.5.2 | 9 / 10 | |
| 5.5.1 | 9 / 10 | |
| 5.5.0 | 9 / 10 | |
| 5.4.3 | 9 / 10 | |
| 5.4.1 | 9 / 10 | |
| 5.4.0 | 9 / 10 | |
| 5.3.2 | 8 / 10 | |
| 5.3.1 | 8 / 10 | |
| 5.3.0 | 8 / 10 | |
| 5.2.5 | 8 / 10 | |
| 5.2.4 | 8 / 7 | |
| 5.2.3 | 8 / 7 | |
| 5.2.2 | 8 / 7 | |
| 5.2.1 | 8 / 7 | |
| 5.1.1 | 8 / 7 | |
| 5.1.0 | 8 / 7 | |
| 5.0.2 | 8 / 7 | |
| 5.0.0 | 8 / 7 | |
| 4.27.0 | 15 / 0 | |
| 4.26.0 | 15 / 0 | |
| 4.25.3 | 15 / 0 | |
| 4.25.2 | 15 / 0 |
v5.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.52.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.50.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.50.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.49.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.49.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.49.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.48.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.48.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.48.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.47.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.46.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.46.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.46.2
2 findingsThis version was published by a different npm account than previous versions on 2025-12-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.46.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-11-15. This could indicate a legitimate maintainer transition or an account compromise.
v5.14.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-11-15. This could indicate a legitimate maintainer transition or an account compromise.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.27.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eric-zaharia.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fluf.
This version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shortcuts.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shortcuts.