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

plccheck

v2.10.1

Published

Siemens PLC language checker + LSP CLI (SCL/ST/LAD/FBD, etc.)

Readme

plccheck

CLI wrapper for the Siemens PLC checker/LSP written in Go.

Documentation: danielv123.github.io/vscode_siemens/docs

Usage

npx plccheck check ./path/to/project

Commands

  • plccheck serve (LSP server over stdio)
  • plccheck check <files-or-folders...>
  • plccheck emit --target <language> <file>
  • plccheck test [--filter <text>] [--events-json] [--coverage-json <file>] [--coverage-lcov <file>] <file-or-folder>
  • plccheck tia <list|export|import|repair-library-dependencies|online|offline|snapshot|compile|download|trust> ...
  • plccheck version

Testing and Coverage

Run tests for a PLC root:

npx plccheck test ./my-plc-project

Request coverage artifacts in JSON and LCOV formats:

npx plccheck test ./my-plc-project --coverage-json coverage.json --coverage-lcov coverage.info

For zero-config discovery in the Coverage Gutters VS Code extension, write the LCOV tracefile as lcov.info instead:

npx plccheck test ./my-plc-project --coverage-json coverage.json --coverage-lcov lcov.info

Note: --events-json prints a stream of execution events to stdout, while --coverage-json writes a finalized coverage report to a file. Coverage artifacts include statement, function, and branch data where runtime data is available. For AI analysis, use the file artifact from --coverage-json.

TIA Portal Openness

On Windows x64 machines with TIA Portal Openness V21 or newer, plccheck tia can attach to a running TIA project or open an explicit .ap21/.zap21 path.

npx plccheck tia trust --json
npx plccheck tia export --project Demo.ap21 --out exported --plc PLC_1 --delete-stale
npx plccheck tia import --project Demo.ap21 --root exported "exported/PLC_1/Program blocks/Main.scl" --create
npx plccheck tia import --project Demo.ap21 --root exported --skip-library-instances "exported/PLC_1"
npx plccheck tia import --project Demo.ap21 --root exported "exported/PLC_1/Program blocks"
npx plccheck tia repair-library-dependencies --project Demo.ap21 --plc PLC_1 --owner CA
npx plccheck tia compile --project Demo.ap21 --plc PLC_1 --json
npx plccheck tia online --project Demo.ap21 --plc PLC_1
npx plccheck tia online --project Demo.ap21 --plc PLC_1 --online-auth-type ProjectUser --online-user engineer --online-password-env TIA_PROJECT_PASSWORD
npx plccheck tia offline --project Demo.ap21 --plc PLC_1
npx plccheck tia snapshot --project Demo.ap21 --plc PLC_1 --json
npx plccheck tia download --project Demo.ap21 --plc PLC_1 --json

export writes PLC roots with .plc.json files and the TIA folder structure. import accepts one or more source files or folders, expands folders recursively, and needs --create before creating missing TIA folders or blocks. Supported direct import sources are .scl, .s7dcl, .db, .udt, .xml, .awl, .lad, and .fbd; pass the owning source file instead of .s7res resource sidecars or .meta.json metadata sidecars. Import refuses to overwrite an existing project-library type instance or one of its project-library dependencies by default; pass --skip-library-instances to leave those library-owned targets unchanged and continue importing the rest, or pass --allow-library-instance-overwrite only for an intentional mutation run. repair-library-dependencies is the safe repair path for that failure class: it recreates the named library instance's project-local dependency objects from the project library. snapshot uses TIA's online DB snapshot before moving retained values to start values, skipping safety DBs and DBs without retained members. download compiles first, uses the project-configured target, reports the selected target in JSON, and falls back to software-only changes when Siemens Openness rejects a full load because of fail-safe data.

Device actions automatically accept non-secret TLS and online-authentication modes. If the PLC requires a project/global/password user, pass --online-auth-type, --online-user where applicable, and --online-password-env <env> so the password is read from an environment variable. Without flags, the bridge also reads PLCCHECK_TIA_ONLINE_USER_TYPE or PLCCHECK_TIA_ONLINE_AUTH_TYPE, PLCCHECK_TIA_ONLINE_USER, and PLCCHECK_TIA_ONLINE_PASSWORD.

Use tia trust --install to install the Siemens Openness AllowList entry for the packaged bridge after reviewing the tia trust --json output. Installation writes HKLM and may require Windows administrator approval through UAC. If the UAC relaunch path is blocked, save the returned registryFile content as a .reg file and import it from an already elevated shell.