@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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
2 findingsThis 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.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.