@spectrum-web-components/dialog
`sp-dialog` displays important information that users need to acknowledge. They appear over the interface and block further interactions. When used directly the `sp-dialog` element surfaces a `slot` based API for deep customization of the content to be in
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Adobe monorepo publishes via GitHub Actions CI/CD with SLSA attestation; publisher-changed to GHA is expected and stable. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Adobe org maintainer additions are routine for this large monorepo; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/button | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/shared | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/divider | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/base | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/alert-dialog | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/button-group | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/icons-workflow | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/underlay | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai | |
| dependencies | unvetted-dep:@spectrum-web-components/modal | AI (dependencies): Same-monorepo sibling dep from Adobe's spectrum-web-components; stable false positive. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.12.2 | 9 / 0 | |
| 1.12.1 | 9 / 0 | |
| 1.12.0 | 9 / 0 | |
| 1.11.2 | 9 / 0 | |
| 1.11.1 | 9 / 0 | |
| 1.11.0 | 9 / 0 | |
| 1.10.0 | 9 / 0 | |
| 1.9.1 | 9 / 0 | |
| 1.9.0 | 9 / 0 | |
| 1.8.0 | 9 / 0 | |
| 1.7.0 | 9 / 0 | |
| 1.6.0 | 9 / 1 | |
| 1.5.0 | 9 / 1 | |
| 1.4.0 | 9 / 1 | |
| 1.3.0 | 9 / 1 | |
| 1.0.2 | 9 / 1 | |
| 1.0.1 | 9 / 1 | |
| 1.0.0 | 9 / 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
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 2025-03-13, 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.