← Home

@spectrum-web-components/action-button

An `<sp-action-button>` represents an action a user can take.

6
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

caseyisonittaratadoberajrock38jnjoshnikkimkrubencjianliao79pvashishpatrickfulton

Keywords

design-systemspectrumadobeadobe-spectrumweb componentsweb-componentslit-elementlit-htmlcomponentcss

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@spectrum-web-components/shared AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
1.12.1 5 / 0
1.12.0 5 / 0
1.11.2 5 / 0
1.8.0 5 / 0
1.7.0 5 / 0
1.6.0 5 / 1

v1.12.1

1 finding
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.12.0

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