← Home

@sitecore-jss/sitecore-jss

npm Repository Homepage

This module is provided as a part of Sitecore JavaScript Rendering SDK. It contains the core JSS APIs (layout service) and utilities.

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

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:chalk AI (phantom-deps): chalk is listed as a runtime dependency in package.json; phantom-dep finding is a false positive for this package. ai

Versions (showing 30 of 30)

Version Deps Published
22.12.4 7 / 26
22.12.3 7 / 26
22.12.1 7 / 26
22.12.0 7 / 26
22.11.0 7 / 26
22.10.0 7 / 26
22.9.1 7 / 26
22.9.0 7 / 26
22.8.0 7 / 26
22.7.0 7 / 26
22.6.0 7 / 26
22.5.5 7 / 23
22.5.4 7 / 23
22.5.3 7 / 23
22.5.2 7 / 23
22.5.1 7 / 23
22.5.0 7 / 23
22.4.1 7 / 23
22.4.0 7 / 23
22.3.1 8 / 23
22.3.0 8 / 22
22.2.1 8 / 22
22.2.0 8 / 22
22.1.4 8 / 22
22.1.3 8 / 22
22.1.2 8 / 22
22.1.1 8 / 22
22.1.0 8 / 22
21.11.0 8 / 22
21.10.1 8 / 22

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

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 2025-01-23, known maintainer) provenance

This version was published by a different npm account (sitecorecorporation) than the most recent previously approved version (sc_illiakovalenko) on 2025-01-23, 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.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

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

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.

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.