npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cspell/cspell-junit-reporter

v10.3.5

Published

JUnit XML reporter for CSpell

Readme

@cspell/cspell-junit-reporter

CSpell reporter with JUnit XML output

Emits a JUnit compatible XML report of a cspell run, suitable for consumption by CI systems (GitHub Actions, GitLab, Jenkins, CircleCI, etc.) that understand the JUnit test result format.

Installation

Install it as a development package in the repository that will use it.

npm install -SD @cspell/cspell-junit-reporter

Usage

Using Command Line

cspell . --reporter @cspell/cspell-junit-reporter

Using CSpell Configuration

Add this to cspell.yaml:

reporters: [['@cspell/cspell-junit-reporter', { outFile: 'cspell-junit.xml' }]]

or cspell.json

{
  "reporters": [["@cspell/cspell-junit-reporter", { "outFile": "cspell-junit.xml" }]]
}

Output format

@cspell/cspell-junit-reporter maps a cspell run onto JUnit XML as follows:

  • one <testsuites> root element for the whole run
  • one <testsuite> per file checked, named after the file
  • one <testcase> per spelling issue found in a file, containing a <failure> with the misspelled word, location, and message
  • a file with no issues gets a single passing <testcase> so the suite is never empty
  • a skipped file gets a single <testcase> containing a <skipped> element
  • processing errors that are not tied to a specific spelling issue (for example, a bad config file) are reported in a dedicated cspell-errors testsuite using <error> instead of <failure>

All file paths, words, and messages are escaped so the output is valid XML even when they contain & < > " ' characters.

Example output for a single file with one issue:

<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="cspell" tests="1" failures="1" errors="0" time="0.001">
  <testsuite name="src/example.ts" tests="1" failures="1" errors="0" time="0.001">
    <testcase name="teh (3:5)" classname="src/example.ts">
      <failure type="spelling" message="Unknown word: &quot;teh&quot;">Unknown word: "teh"</failure>
    </testcase>
  </testsuite>
</testsuites>

Settings

Possible settings:

  • outFile (default: stdout) - path for the XML file to emit
  • suiteName (default: cspell) - name used for the root <testsuites> element