← Home

@sitecore-jss/sitecore-jss-proxy

npm Homepage

Middlewares, utilities to work in a headless mode

9
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

darusc_illiakovalenkoappadmin-svcsc-artemalexeyenkoapathaniasc-yavorkrastevsitecorecorporationsc-maximnakhodsc-menelaosnasies

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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
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
bogus-package bogus-package AI (bogus-package): Established Sitecore JSS library; sparse README/keywords is a documentation style choice, not spam. ai

Versions (showing 9 of 9)

Version Deps Published
22.12.1 6 / 19
22.10.0 6 / 19
22.9.1 6 / 19
22.9.0 6 / 19
22.8.0 6 / 19
22.7.0 6 / 19
22.6.0 6 / 19
21.11.0 3 / 12
21.10.1 3 / 12

v22.12.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.10.0

1 finding
LOW No provenance attestation provenance

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

v22.9.1

1 finding
LOW No provenance attestation provenance

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

v22.9.0

1 finding
LOW No provenance attestation provenance

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

v22.8.0

1 finding
LOW No provenance attestation provenance

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

v22.7.0

1 finding
LOW No provenance attestation provenance

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

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

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

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