Summary
Togoder Security scanned the npm package dom-accessibility-api@0.6.3 on Oct 6, 2026. An AI review of 22 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/accessible-description.js | safe | No malicious patterns detected; this is a legitimate Babel-compiled accessibility utility computing ARIA descriptions. |
| dist/accessible-description.mjs | safe | No malicious patterns detected; the code is a standard Babel-compiled accessibility utility with no network, filesystem, process, or dynamic execution behavior. |
| dist/accessible-name-and-description.js | safe | No malicious patterns detected; this is a standard accessible name and description computation library that only reads DOM attributes and styles. |
| dist/accessible-name-and-description.mjs | safe | No malicious patterns detected; the code implements accessible name computation per W3C accname specification with no data exfiltration, network calls, process spawning, or obfuscated/dynamic code execution. |
| dist/accessible-name.js | safe | No malicious patterns detected |
| dist/accessible-name.mjs | safe | Cleared by Jev triage; no further analysis needed |
| dist/getRole.js | safe | No malicious patterns detected; the code is a standard ARIA role utility for DOM elements with no network, filesystem, process, or dynamic execution behavior. |
| dist/getRole.mjs | safe | The code is a pure accessibility helper for determining ARIA roles and contains no malicious patterns such as exfiltration, code execution, or system manipulation. |
| dist/index.js | safe | No malicious patterns detected; the file is a standard compiled re-export module with benign dependency imports. |
| dist/index.mjs | safe | No malicious patterns detected |
| dist/is-disabled.js | safe | The file contains a simple, legitimate utility function for checking whether an HTML element is disabled, with no malicious patterns, network activity, or code execution. |
| dist/is-disabled.mjs | safe | No malicious patterns detected |
| dist/is-inaccessible.js | safe | No malicious patterns detected |
| dist/is-inaccessible.mjs | safe | No malicious patterns detected |
| dist/polyfills/SetLike.js | safe | No malicious patterns detected |
| dist/polyfills/SetLike.mjs | safe | No malicious patterns detected |
| dist/polyfills/array.from.js | safe | No malicious patterns detected |
| dist/polyfills/array.from.mjs | safe | Cleared by Jev triage; no further analysis needed |
| dist/polyfills/iterator.d.js | safe | No malicious patterns detected |
| dist/polyfills/iterator.d.mjs | safe | No malicious patterns detected |
| dist/util.js | safe | No malicious patterns detected |
| dist/util.mjs | safe | No malicious patterns detected |
Affected version ranges
None of the 2 scanned versions of dom-accessibility-api are flagged high or critical. The latest scanned version, 0.6.3, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 0.5.16 – 0.6.3 | No issues | 2 | >=0.5.16 <=0.6.3 | |
| 0.5.10 | Not scanned | 1 | 0.5.10 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of dom-accessibility-api
Frequently asked questions
Is dom-accessibility-api safe to use?
Our AI source review of dom-accessibility-api@0.6.3 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does dom-accessibility-api contain malware?
No malware was identified in dom-accessibility-api@0.6.3 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was dom-accessibility-api checked?
Togoder Security downloaded the published npm package and had an AI model read its 22 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan dom-accessibility-api together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in dom-accessibility-api@0.6.3, cost nothing.