← Home

@adobe/magento-storefront-events-sdk

SDK for working with events on an Adobe Commerce storefront

10
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

marbectripodgarthdblazdadobe-adminpatrickfultontrieloffshazronkrisnyedcpfsdknatebaldwindevongovettaspro83symanovidpfisterstefan-guggisbergrofekptdobeadobehallsfullcolorcoderdjaeggidylandepassmhaackamol-anandstopp-adobedotenduh_schmidtasthabh23zdahbituicufmeschbe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Adobe monorepo team rotation; publisher track record strong, no behavioral change. ai
maintainer-change maintainer-removed AI (maintainer-change): Same rotation; no malicious diff accompanies removal. ai
publish-pattern dormant-publish AI (publish-pattern): Long-lived official package with sporadic release cadence, no diff anomalies. ai
dependencies unvetted-dep:@adobe/adobe-client-data-layer AI (dependencies): First-party Adobe dependency used consistently across all versions of this package; stable false positive. ai

Versions (showing 10 of 10)

Version Deps Published
1.17.0 1 / 20
1.16.0 1 / 20
1.15.0 1 / 20
1.14.1 1 / 20
1.14.0 1 / 20
1.13.0 1 / 20
1.12.0 1 / 20
1.11.0 1 / 20
1.10.0 1 / 20
1.9.0 1 / 20

v1.13.0

1 finding
LOW No provenance attestation provenance

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

v1.12.0

1 finding
LOW No provenance attestation provenance

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

v1.11.0

1 finding
LOW No provenance attestation provenance

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

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

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