← Home

@swc-react/underlay

npm Repository Homepage

React and Next.js wrapper of the @spectrum-web-components/underlay component

10
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jnjoshtaratadoberajrock38nikkimkrubencjianliao79pvashishpatrickfultoncaseyisonit

Keywords

ReactSpectrum Web Components@spectrum-web-components/underlay

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI with SLSA attestation is a legitimate supply-chain improvement for this Adobe package. ai
provenance no-provenance AI (provenance): Adobe SWC React wrappers consistently publish without Sigstore provenance; stable pattern across all versions. ai

Versions (showing 10 of 10)

Version Deps Published
1.12.0 2 / 0
1.11.2 2 / 0
1.11.1 2 / 0
1.11.0 2 / 0
1.10.0 2 / 0
1.9.1 2 / 0
1.9.0 2 / 0
1.8.0 2 / 0
1.7.0 2 / 0
1.6.0 2 / 0

v1.12.0

2 findings
HIGH Publisher changed: rubenc → GitHub Actions (on 2026-05-12) provenance

This version was published by a different npm account than previous versions on 2026-05-12. 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.2

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

v1.9.0

2 findings
HIGH Publisher changed: caseyisonit → taratadobe (on 2025-10-13) provenance

This version was published by a different npm account than previous versions on 2025-10-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.8.0

2 findings
HIGH Publisher changed: caseyisonit → rubenc (on 2025-09-23) provenance

This version was published by a different npm account than previous versions on 2025-09-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.7.0

2 findings
HIGH Publisher changed: caseyisonit → rubenc (on 2025-06-11) provenance

This version was published by a different npm account than previous versions on 2025-06-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

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