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

jclcheck

v1.0.0

Published

Check z/OS JCL without a mainframe: a lexer, parser and rule engine based on the IBM JCL Reference, a formatter, and the jclcheck command (text, JSON and SARIF output). No dependencies.

Downloads

90

Readme

jclcheck

Check z/OS JCL without a mainframe. jclcheck reads JCL the way z/OS does (80-column records, continuations, in-stream data, JES2 and JES3 statements) and reports each problem with its line and column, a code, a plain-English explanation and a suggested fix. It is the engine behind jclcheck.xyz, and it has no dependencies.

It is static checking only: nothing is run, and datasets and catalogued procedures can't be confirmed to exist unless you supply the procedures.

Command line

Node 22 or later.

npx jclcheck jcl/*.jcl                       # file:line:column  severity  code  message
npx jclcheck "jcl/**/*.jcl" --format sarif > jclcheck.sarif
npx jclcheck format jcl/payroll.jcl          # print it laid out in the usual columns
npx jclcheck format --write jcl/*.jcl        # or rewrite the files

| Option | What it does | |---|---| | --zos <level> | The z/OS level to check against: 2.3, 2.4, 2.5, 3.1 or 3.2 (the default). | | --jes <JES2\|JES3> | The JES to check for (JES3 only at z/OS 2.5 and earlier). | | --library <dir> | Catalogued PROCs and INCLUDE members, one file per member (MYPROC.jcl). A subdirectory named like a library (MY.PROCS.JCL/) is that library, searched in the job's JCLLIB order. | | --profile <file> | A site profile, as JSON (below). | | --format text\|json\|sarif | Text (the default), JSON ({ files: [{ file, diagnostics, stats }] }) or SARIF 2.1.0. | | --max-warnings <n> | Also fail when there are more warnings than this. |

It exits with 0 when there are no errors, 1 when a file has an error or there are too many warnings, and 2 when it can't run (a bad option, or a file it can't read; the other files are still checked). Quoted globs (*, **, ?) are expanded by the command itself.

GitHub Actions

Each diagnostic shows on its line of the pull request:

name: JCL
on: [pull_request]
jobs:
  jclcheck:
    runs-on: ubuntu-latest
    permissions:
      security-events: write
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22
      - run: npx jclcheck "jcl/**/*.jcl" --format sarif > jclcheck.sarif
      - uses: github/codeql-action/upload-sarif@v3
        if: always()
        with:
          sarif_file: jclcheck.sarif

In your own code

const { validate, format } = require('jclcheck');

const result = validate(source, { zosLevel: '3.1', jes: 'JES2' });
for (const d of result.diagnostics) {
    console.log(`${d.line}:${d.column} ${d.severity} ${d.code} ${d.message}`);
}
console.log(result.stats.valid); // true when there are no errors

const { text, changed, notes, refused } = format(source);

validate(source, options) takes zosLevel, jes, library (a list of { dsn, member, source } catalogued procedures and INCLUDE members) and profile. It returns { diagnostics, ast, datasets, stats, zosLevel, jes }. Each diagnostic has code, severity (error, warning or info), line, column, length, message, suggestion and source, plus member when it is inside a library member and suppressed: true when a comment hid it.

The package also exports keywordHelp(zosLevel) (plain-English descriptions of every keyword), profileProblem(profile) and the supported levels (ZOS_LEVELS, DEFAULT_ZOS_LEVEL, isZosLevel, ...).

Suppressions and site profile

//* JCLCHECK OFF-NEXT JCLK001 hides that code on the next statement, and //* JCLCHECK OFF JCLK001 hides it until //* JCLCHECK ON JCLK001 or the end of the job. They are JCL comments, so the job still runs unchanged. A site profile adds your shop's rules:

{
  "names": { "job": ["AR*"], "step": "STEP%%" },
  "allowed": { "CLASS": ["A", "B"] },
  "dsnPrefixes": ["AR", "SYS1"],
  "extraKeywords": { "EXEC": ["LOCALKW"] },
  "severity": { "JCLS014": "off", "JCLK001": "error" }
}

Usage counting

Off unless you opt in with JCLCHECK_TELEMETRY=1 or --telemetry, and DO_NOT_TRACK=1 always turns it off. An opted-in run sends one small list of events (version, Node major version, OS, CI system, number of files, result, format, options used and diagnostic codes, never any JCL or file names), with a 1-second limit. JCLCHECK_TELEMETRY=debug prints the list and sends nothing.

Links

  • Workbench: https://jclcheck.xyz
  • Source and issues: https://github.com/Zubs/jclcheck

MIT licensed.