← Home

@remote-dom/core

npm Repository Homepage
8
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

shopify-deplemonmade

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Shopify's remote-dom repo uses GitHub Actions CI with SLSA attestation for publishing; transition from shopify-dep to GH Actions is expected. ai
publish-pattern rapid-publish AI (publish-pattern): Automated CI releasing a monorepo publishes multiple packages in rapid succession; stable pattern for this package. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped Shopify package; name similarity to 'cors' is coincidental, not a typosquat. ai

Versions (showing 8 of 8)

Version Deps Published
1.11.1 2 / 2
1.11.0 2 / 2
1.10.1 2 / 2
1.10.0 2 / 2
1.9.0 2 / 2
1.8.1 2 / 2
1.8.0 2 / 2
1.7.1 2 / 2

v1.11.1

2 findings
HIGH Publisher changed: shopify-dep → GitHub Actions (on 2026-05-08) provenance

This version was published by a different npm account than previous versions on 2026-05-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.11.0

2 findings
HIGH Publisher changed: shopify-dep → GitHub Actions (on 2026-05-01) provenance

This version was published by a different npm account than previous versions on 2026-05-01. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.1

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

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