@sitecore-jss/sitecore-jss-proxy Apache-2.0 28 versions

@sitecore-jss/sitecore-jss-proxy

npm Homepage

Middlewares, utilities to work in a headless mode

28

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

darusc_illiakovalenkoappadmin-svcsc-artemalexeyenkoapathaniasitecorecorporationsc-maximnakhodsc-menelaosnasies

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Long gap reflects major version cadence for Sitecore JSS product; not indicative of account takeover given publisher track record.	ai	2026/05/07
publish-pattern	new-deps-added	AI (publish-pattern): New @sitecore-cloudsdk/* deps are first-party Sitecore packages consistent with documented v22 personalization feature additions.	ai	2026/05/07
bogus-package	bogus-package	AI (bogus-package): Established Sitecore JSS library; sparse README/keywords is a documentation style choice, not spam.	ai	2026/05/02

Versions (showing 28 of 28)

Version	Deps	Published
22.12.4	6 / 19	2026-07-14
22.12.3	6 / 19	2026-05-04
22.12.1	6 / 19	2026-04-07
22.10.0	6 / 19	2025-11-24
22.9.1	6 / 19	2025-09-24
22.9.0	6 / 19	2025-08-20
22.8.0	6 / 19	2025-07-07
22.7.0	6 / 19	2025-06-17
22.6.0	6 / 19	2025-05-07
22.5.5	6 / 19	2025-04-25
22.5.4	6 / 19	2025-03-21
22.5.3	6 / 19	2025-03-19
22.5.2	6 / 19	2025-03-03
22.5.1	6 / 19	2025-02-27
22.5.0	6 / 19	2025-02-11
22.4.1	6 / 19	2025-01-28
22.4.0	6 / 19	2025-01-23
22.3.1	6 / 19	2024-12-09
22.3.0	3 / 12	2024-11-24
22.2.1	3 / 12	2024-11-13
22.2.0	3 / 12	2024-11-05
22.1.4	3 / 12	2024-10-21
22.1.3	3 / 12	2024-09-05
22.1.2	3 / 12	2024-09-02
22.1.1	3 / 12	2024-08-28
22.1.0	3 / 12	2024-08-20
21.11.0	3 / 12	2025-11-24
21.10.1	3 / 12	2025-11-11

v22.12.4

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: sc-artemalexeyenko → sc_illiakovalenko (on 2026-07-14, known maintainer) provenance

This version was published by a different npm account (sc_illiakovalenko) than the most recent previously approved version (sc-artemalexeyenko) on 2026-07-14, but sc_illiakovalenko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v22.12.3

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: sc_illiakovalenko → sc-artemalexeyenko (on 2026-05-04, known maintainer) provenance

This version was published by a different npm account (sc-artemalexeyenko) than the most recent previously approved version (sc_illiakovalenko) on 2026-05-04, but sc-artemalexeyenko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v22.5.5

1 finding

LOW No provenance attestation provenance

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

v22.5.4

1 finding

LOW No provenance attestation provenance

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

v22.5.3

1 finding

LOW No provenance attestation provenance

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

v22.5.2

1 finding

LOW No provenance attestation provenance

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

v22.5.1

1 finding

LOW No provenance attestation provenance

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

v22.5.0

1 finding

LOW No provenance attestation provenance

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

v22.4.1

1 finding

LOW No provenance attestation provenance

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

v22.4.0

1 finding

LOW No provenance attestation provenance

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

v22.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: sc_illiakovalenko → sitecorecorporation (on 2024-12-09, known maintainer) provenance

This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2024-12-09, but sitecorecorporation is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v22.3.0

1 finding

LOW No provenance attestation provenance

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

v22.2.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: sc-yavorkrastev → sc_illiakovalenko (on 2024-11-13, known maintainer) provenance

This version was published by a different npm account (sc_illiakovalenko) than the most recent previously approved version (sc-yavorkrastev) on 2024-11-13, but sc_illiakovalenko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v22.2.0

1 finding

LOW No provenance attestation provenance

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

v22.1.4

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: sc_illiakovalenko → sc-yavorkrastev (on 2024-10-21, known maintainer) provenance

This version was published by a different npm account (sc-yavorkrastev) than the most recent previously approved version (sc_illiakovalenko) on 2024-10-21, but sc-yavorkrastev is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v22.1.3

1 finding

LOW No provenance attestation provenance

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

v22.1.2

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: apathania → sc_illiakovalenko (on 2024-09-02, known maintainer) provenance

This version was published by a different npm account (sc_illiakovalenko) than the most recent previously approved version (apathania) on 2024-09-02, but sc_illiakovalenko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v22.1.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: sc-artemalexeyenko → apathania (on 2024-08-28, known maintainer) provenance

This version was published by a different npm account (apathania) than the most recent previously approved version (sc-artemalexeyenko) on 2024-08-28, but apathania is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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