Summary
Togoder Security scanned the npm package dom-accessibility-api@0.5.16 on Oct 6, 2026. An AI review of 20 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; the file contains standard Babel-compiled accessibility utility code with no network, filesystem, or process activity. |
| dist/accessible-description.mjs | safe | No malicious patterns detected |
| dist/accessible-name-and-description.js | safe | No malicious patterns detected |
| dist/accessible-name-and-description.mjs | safe | No malicious patterns detected; the code is a legitimate implementation of the W3C accessible name and description computation algorithm. |
| dist/accessible-name.js | safe | No malicious patterns detected; code is a benign accessible name computation utility. |
| dist/accessible-name.mjs | safe | No malicious patterns detected; the code is a legitimate accessibility utility implementing the W3C AccName specification. |
| dist/getRole.js | safe | No malicious patterns detected |
| dist/getRole.mjs | safe | No malicious patterns detected; the code is a legitimate utility for determining ARIA roles from DOM elements, with no network, filesystem, process, or dynamic execution concerns. |
| dist/index.js | safe | No malicious patterns detected |
| dist/index.mjs | safe | The file only contains static re-exports of local modules with no executable code or malicious patterns. |
| 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; the file is a legitimate Babel-compiled Set polyfill with no network, filesystem, credential, or dynamic code execution behavior. |
| dist/polyfills/SetLike.mjs | safe | No malicious patterns detected; this is a standard Babel-transpiled Set polyfill implementation. |
| 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; the code contains standard DOM utility functions for element checking, role querying, and safeWindow access with no network, filesystem, process, or dynamic execution activity. |
| 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.5.16 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.5.16 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 20 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.5.16, cost nothing.