Scan your whole stack
Latest version: v33.0.2
@atlaskit/editor-plugin-help-dialog was last scanned on 18 Nov 2026 at version 33.0.2. Risk score 0 of 100. No malicious behavior was detected.
| Version | Published | Status |
|---|---|---|
| 33.0.2 LATEST | 18 Nov 2026 | No rules fired |
| 33.0.1 | 17 Nov 2026 | No rules fired |
| 33.0.0 | 17 Nov 2026 | No rules fired |
| 32.0.0 | 17 Nov 2026 | Not shown |
| 30.0.20 | 13 Nov 2026 | Not shown |
Findings for v33.0.2. The score is a capped sum of the weights of the rules that fired — not CVSS, not exploitability, and not a probability. It is not comparable across packages with different scan coverage.
The score describes 33.0.2; other versions have their own rules, not their own score.
The publisher’s own README, as collected from the registry.
Help Dialog plugin for @atlaskit/editor-core
Note: This component is designed for internal Atlassian development. External contributors will be able to use this component but will not be able to submit issues.
The Help Dialog plugin provides an interactive modal interface that displays helpful information about editor features, keyboard shortcuts, and formatting options. It integrates with the editor's quick insert functionality and supports dynamic configuration based on available features like image uploads and AI capabilities.
Internal use only
@atlaskit/editor-plugin-help-dialog is intended for internal use by the @atlaskit/editor-core and as a plugin dependency of the Editor within your product.
Direct use of this component is not supported.
Please see Atlaskit - Editor plugin Help Dialog for documentation and examples for this package.
For internal Atlassian, visit the slack channel #help-editor for support or visit go/editor-help to submit a bug.
Please see Atlassian Frontend - License for more licensing information.
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.
The probe returned only these fields for this server — auth requirement, protocol and tool list weren’t observed, so they’re not shown (never guessed).
The publisher’s own links, as the registry reports them. These are not sources for the assessment on this page.