@omegagrid/dialog
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ts-debounce | AI (phantom-deps): Declared runtime dep referenced in config; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:monaco-editor | AI (phantom-deps): Declared runtime dep referenced in config; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:vscode-loader | AI (phantom-deps): Declared runtime dep referenced in config; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Declared runtime dep referenced in config; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 100 of 482)
| Version | Deps | Published |
|---|---|---|
| 0.6.89 | 7 / 10 | |
| 0.6.88 | 7 / 10 | |
| 0.6.87 | 7 / 10 | |
| 0.6.86 | 7 / 10 | |
| 0.6.85 | 7 / 10 | |
| 0.6.84 | 7 / 10 | |
| 0.6.83 | 7 / 10 | |
| 0.6.82 | 7 / 10 | |
| 0.6.81 | 7 / 10 | |
| 0.6.80 | 7 / 10 | |
| 0.6.79 | 7 / 10 | |
| 0.6.78 | 7 / 10 | |
| 0.6.77 | 7 / 10 | |
| 0.6.76 | 7 / 10 | |
| 0.6.75 | 7 / 10 | |
| 0.6.74 | 7 / 10 | |
| 0.6.73 | 7 / 10 | |
| 0.6.72 | 7 / 10 | |
| 0.6.71 | 7 / 10 | |
| 0.6.70 | 7 / 10 | |
| 0.6.69 | 7 / 10 | |
| 0.6.68 | 7 / 10 | |
| 0.6.67 | 7 / 10 | |
| 0.6.66 | 7 / 10 | |
| 0.6.65 | 7 / 10 | |
| 0.6.64 | 7 / 10 | |
| 0.6.63 | 7 / 10 | |
| 0.6.62 | 7 / 10 | |
| 0.6.61 | 7 / 10 | |
| 0.6.60 | 7 / 10 | |
| 0.6.59 | 7 / 10 | |
| 0.6.58 | 7 / 10 | |
| 0.6.57 | 7 / 10 | |
| 0.6.56 | 7 / 10 | |
| 0.6.55 | 7 / 10 | |
| 0.6.54 | 7 / 10 | |
| 0.6.53 | 7 / 10 | |
| 0.6.52 | 7 / 10 | |
| 0.6.51 | 7 / 10 | |
| 0.6.50 | 7 / 10 | |
| 0.6.49 | 7 / 10 | |
| 0.6.48 | 7 / 10 | |
| 0.6.47 | 7 / 10 | |
| 0.6.46 | 7 / 10 | |
| 0.6.45 | 7 / 10 | |
| 0.6.44 | 7 / 10 | |
| 0.6.43 | 7 / 10 | |
| 0.6.42 | 7 / 10 | |
| 0.6.41 | 7 / 10 | |
| 0.6.40 | 7 / 10 | |
| 0.6.39 | 7 / 10 | |
| 0.6.38 | 7 / 10 | |
| 0.6.37 | 7 / 10 | |
| 0.6.36 | 7 / 10 | |
| 0.6.35 | 7 / 10 | |
| 0.6.34 | 7 / 10 | |
| 0.6.33 | 7 / 10 | |
| 0.6.32 | 7 / 10 | |
| 0.6.31 | 7 / 10 | |
| 0.6.30 | 7 / 10 | |
| 0.6.29 | 7 / 10 | |
| 0.6.28 | 7 / 10 | |
| 0.6.27 | 7 / 10 | |
| 0.6.26 | 7 / 10 | |
| 0.6.25 | 7 / 10 | |
| 0.6.24 | 7 / 10 | |
| 0.6.23 | 7 / 10 | |
| 0.6.22 | 7 / 10 | |
| 0.6.21 | 7 / 10 | |
| 0.6.20 | 7 / 10 | |
| 0.6.19 | 7 / 10 | |
| 0.6.18 | 7 / 10 | |
| 0.6.17 | 7 / 10 | |
| 0.6.16 | 7 / 10 | |
| 0.6.15 | 7 / 10 | |
| 0.6.14 | 7 / 10 | |
| 0.6.13 | 7 / 10 | |
| 0.6.12 | 7 / 10 | |
| 0.6.11 | 7 / 10 | |
| 0.6.10 | 7 / 10 | |
| 0.6.9 | 7 / 10 | |
| 0.6.8 | 7 / 10 | |
| 0.6.7 | 7 / 10 | |
| 0.6.6 | 7 / 10 | |
| 0.6.5 | 7 / 10 | |
| 0.6.4 | 7 / 10 | |
| 0.6.3 | 7 / 10 | |
| 0.6.2 | 7 / 10 | |
| 0.6.1 | 7 / 10 | |
| 0.6.0 | 7 / 10 | |
| 0.5.20 | 7 / 10 | |
| 0.5.19 | 7 / 10 | |
| 0.5.18 | 7 / 10 | |
| 0.5.17 | 7 / 10 | |
| 0.5.16 | 7 / 10 | |
| 0.5.15 | 7 / 10 | |
| 0.5.14 | 7 / 10 | |
| 0.5.13 | 7 / 10 | |
| 0.5.12 | 7 / 10 | |
| 0.5.11 | 7 / 10 |
v0.6.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.