@spectrum-web-components/button
An `<sp-button>` represents an action a user can take. sp-buttons can be clicked or tapped to perform an action or to navigate to another page. Buttons in Spectrum have several variations for different uses and multiple levels of loudness for various atte
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@spectrum-web-components/base | AI (phantom-deps): Monorepo sibling dep, same org scope. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/icon | AI (phantom-deps): Monorepo sibling dep, same org scope. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/shared | AI (phantom-deps): Monorepo sibling dep, same org scope. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/icons-ui | AI (phantom-deps): Monorepo sibling dep, same org scope. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/clear-button | AI (phantom-deps): Monorepo sibling dep, same org scope. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/close-button | AI (phantom-deps): Monorepo sibling dep, same org scope. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/reactive-controllers | AI (phantom-deps): Monorepo sibling dep, same org scope. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/reactive-controllers | AI (dependencies): Same-monorepo sibling package; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/base | AI (dependencies): Same-monorepo sibling package; coordinated versioning is expected. | ai | |
| phantom-deps | phantom-dep:@spectrum-web-components/progress-circle | AI (phantom-deps): Same-org sibling; may be re-exported or used indirectly via other sibling deps. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icon | AI (dependencies): Same-monorepo sibling package; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/shared | AI (dependencies): Same-monorepo sibling package; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icons-ui | AI (dependencies): Same-monorepo sibling package; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/clear-button | AI (dependencies): Same-monorepo sibling package; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/close-button | AI (dependencies): Same-monorepo sibling package; coordinated versioning is expected. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/progress-circle | AI (dependencies): Same-monorepo sibling package; coordinated versioning is expected. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.12.2 | 8 / 0 | |
| 1.12.1 | 8 / 0 | |
| 1.12.0 | 8 / 0 | |
| 1.11.2 | 8 / 0 | |
| 1.11.1 | 8 / 0 | |
| 1.11.0 | 8 / 0 | |
| 1.10.0 | 8 / 0 | |
| 1.9.1 | 8 / 0 | |
| 1.9.0 | 8 / 0 | |
| 1.8.0 | 8 / 0 | |
| 1.7.0 | 8 / 0 | |
| 1.6.0 | 8 / 1 | |
| 1.5.0 | 8 / 1 | |
| 1.4.0 | 8 / 1 | |
| 1.3.0 | 8 / 1 | |
| 1.2.0 | 8 / 1 | |
| 1.1.2 | 8 / 1 | |
| 1.1.1 | 8 / 1 | |
| 1.1.0 | 8 / 1 | |
| 1.0.3 | 8 / 1 | |
| 1.0.2 | 7 / 1 | |
| 1.0.1 | 7 / 1 | |
| 1.0.0 | 7 / 1 |
v1.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rajrock38) than the most recent previously approved version (rubenc) on 2025-04-15, but rajrock38 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rubenc) than the most recent previously approved version (rajrock38) on 2025-02-27, but rubenc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rajrock38) than the most recent previously approved version (rubenc) on 2025-01-29, but rajrock38 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rajrock38) than the most recent previously approved version (pvashish) on 2025-01-29, but rajrock38 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rubenc) than the most recent previously approved version (pvashish) on 2024-12-09, but rubenc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pvashish) than the most recent previously approved version (rubenc) on 2024-11-26, but pvashish is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rajrock38) than the most recent previously approved version (rubenc) on 2024-11-11, but rajrock38 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.