Security News
Weekly Downloads Now Available in npm Package Search Results
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
axe-sarif-converter
Advanced tools
Convert axe-core accessibility scan results to the SARIF format.
Use this with the Sarif Viewer Build Tab Azure DevOps Extension to visualize accessibility scan results in the build results of an Azure Pipelines build.
Before using axe-sarif-converter, you will need to run an axe accessibility scan to produce some axe results to convert. Typically, you would do this by using an axe integration library for your favorite browser automation tool (axe-puppeteer, axe-webdriverjs, cypress-axe).
axe-sarif-converter exports a single function, named convertAxeToSarif
. Use it like this:
import * as Axe from 'axe';
import * as AxePuppeteer from 'axe-puppeteer';
import * as fs from 'fs';
import * as Puppeteer from 'puppeteer'
import * as util from 'util';
import { convertAxeToSarif, SarifLog } from 'axe-sarif-converter';
test('my accessibility test', async () => {
// This example uses axe-puppeteer, but you can use any axe-based library
// that outputs axe scan results in the default axe output format
const testPage: Puppeteer.Page = /* ... set up your test page ... */;
const axeResults: Axe.AxeResults = await new AxePuppeteer(testPage).analyze();
// Perform the conversion
const sarifResults: SarifLog = convertAxeToSarif(axeResults);
// Output a SARIF file, perhaps for use with a Sarif Viewer tool
await util.promisify(fs.writeFile)(
'./test-results/my-accessibility-test.sarif',
JSON.stringify(sarifResults),
{ encoding: 'utf8' });
}
The microsoft/axe-pipelines-samples project contains full sample code that walks you through integrating this library into your project, from writing a test to seeing results in Azure Pipelines.
The version number of this library is independent from the version numbers of the axe-core inputs and SARIF outputs it supports.
Note that the SARIF format does not use semantic versioning, and there are breaking changes between the v2.0 and v2.1 SARIF formats. If you need compatibility with a SARIF viewer that only supports v2.0, you should use version 1.x of this library.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
FAQs
Convert axe-core accessibility scan results to the SARIF format
The npm package axe-sarif-converter receives a total of 9,678 weekly downloads. As such, axe-sarif-converter popularity was classified as popular.
We found that axe-sarif-converter demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.