@atlaskit/inline-dialog
An inline dialog is a pop-up container for small amounts of information. It can also contain controls.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @atlaskit/* packages; not a third-party supply-chain risk for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit scope phantom dep is a common pattern in Atlassian's monorepo publishing; declared for type resolution but not directly imported at runtime. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam publisher consistently publishes without Sigstore provenance across all @atlaskit packages; this is a stable characteristic of the publisher, not a risk signal. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 18.1.8 | 10 / 20 | |
| 18.1.7 | 10 / 20 | |
| 18.1.6 | 10 / 20 | |
| 18.1.5 | 10 / 20 | |
| 18.1.4 | 10 / 19 | |
| 18.1.3 | 10 / 19 | |
| 18.1.2 | 10 / 19 | |
| 18.1.1 | 10 / 19 | |
| 18.1.0 | 8 / 19 | |
| 18.0.17 | 8 / 19 | |
| 18.0.16 | 8 / 19 | |
| 18.0.15 | 8 / 19 | |
| 18.0.14 | 8 / 18 | |
| 18.0.13 | 8 / 18 | |
| 18.0.12 | 9 / 17 | |
| 18.0.11 | 9 / 17 | |
| 18.0.10 | 9 / 17 | |
| 18.0.9 | 9 / 17 | |
| 18.0.8 | 9 / 17 | |
| 18.0.7 | 9 / 17 | |
| 18.0.6 | 10 / 17 | |
| 18.0.5 | 10 / 17 | |
| 18.0.4 | 10 / 17 | |
| 18.0.3 | 10 / 17 | |
| 18.0.2 | 10 / 17 | |
| 18.0.1 | 10 / 17 | |
| 18.0.0 | 10 / 17 |
v18.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.