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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sdlc.vitechteam/sdlc-pipeline-helper

v0.0.20

Published

SDLC Pipelines Helper

Downloads

3

Readme

SDLC Vitech

Pipelines Helpers

oclif Version Downloads/week License

Usage

$ npm install -g @sdlc.vitechteam/sdlc-pipeline-helper
$ sdlcpipelinehelper COMMAND
running command...
$ sdlcpipelinehelper (-v|--version|version)
@sdlc.vitechteam/sdlc-pipeline-helper/0.0.20 linux-x64 node-v14.19.2
$ sdlcpipelinehelper --help [COMMAND]
USAGE
  $ sdlcpipelinehelper COMMAND
...

Commands

sdlcpipelinehelper check-publish

describe the command here

USAGE
  $ sdlcpipelinehelper check-publish

OPTIONS
  -h, --help                         show CLI help
  --appId=appId                      GitHub application id. Optionally use GH_APP_ID environment variable

  --checkConclusion=checkConclusion  Can be one of action_required, cancelled, failure, neutral, success, skipped,
                                     stale, or timed_out.
                                     When the conclusion is action_required, additional details should be
                                     provided on the site specified by details_url.

  --checkName=checkName              (required) check name

  --checkStatus=checkStatus          [default: completed] check status: queued, in_progress, or completed

  --commit=commit                    (required) commit SHA

  --detailsUrl=detailsUrl            Details URL about build. In our case link to Tekton dashboard.

  --installationId=installationId    GitHub application installationId. Optionally use GH_APP_INSTALLATION_ID
                                     environment variable

  --privateKey=privateKey            GitHub application primate key. Optionally use GH_APP_PRIVATE_KEY environment
                                     variable

  --repoName=repoName                (required) Git repository name

  --repoOwner=repoOwner              (required) Git repository owner

  --summary=summary                  (required) check summary

  --title=title                      (required) check title

See code: src/commands/check-publish.ts

sdlcpipelinehelper cucumber-publish

describe the command here

USAGE
  $ sdlcpipelinehelper cucumber-publish

OPTIONS
  -f, --reportPath=reportPath        [default: **/cucumber_report.json] report paths like: **/cucumber_report.json
  -h, --help                         show CLI help
  --appId=appId                      GitHub application id. Optionally use GH_APP_ID environment variable

  --checkConclusion=checkConclusion  Can be one of action_required, cancelled, failure, neutral, success, skipped,
                                     stale, or timed_out.
                                     When the conclusion is action_required, additional details should be
                                     provided on the site specified by details_url.

  --checkName=checkName              (required) Check Name

  --checkStatus=checkStatus          [default: completed] check status: queued, in_progress, or completed

  --commit=commit                    (required) commit SHA

  --detailsUrl=detailsUrl            Details URL about build. In our case link to Tekton dashboard.

  --installationId=installationId    GitHub application installationId. Optionally use GH_APP_INSTALLATION_ID
                                     environment variable

  --privateKey=privateKey            GitHub application primate key. Optionally use GH_APP_PRIVATE_KEY environment
                                     variable

  --repoFolderName=repoFolderName    [default: source] repository folder name

  --repoName=repoName                (required) Git repository name

  --repoOwner=repoOwner              (required) Git repository owner

  --sourceRootPath=sourceRootPath    [default: /workspace/source] source root path

See code: src/commands/cucumber-publish.ts

sdlcpipelinehelper help [COMMAND]

display help for sdlcpipelinehelper

USAGE
  $ sdlcpipelinehelper help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

sdlcpipelinehelper junit-report-publish

describe the command here

USAGE
  $ sdlcpipelinehelper junit-report-publish

OPTIONS
  -f, --reportPaths=reportPaths      (required) report paths like: **/test-results/**/TEST-*.xml
  -h, --help                         show CLI help
  --appId=appId                      GitHub application id. Optionally use GH_APP_ID environment variable

  --checkConclusion=checkConclusion  Can be one of action_required, cancelled, failure, neutral, success, skipped,
                                     stale, or timed_out.
                                     When the conclusion is action_required, additional details should be
                                     provided on the site specified by details_url.

  --checkName=checkName              (required) Check Name

  --checkStatus=checkStatus          [default: completed] check status: queued, in_progress, or completed

  --commit=commit                    (required) commit SHA

  --detailsUrl=detailsUrl            Details URL about build. In our case link to Tekton dashboard.

  --installationId=installationId    GitHub application installationId. Optionally use GH_APP_INSTALLATION_ID
                                     environment variable

  --privateKey=privateKey            GitHub application primate key. Optionally use GH_APP_PRIVATE_KEY environment
                                     variable

  --repoName=repoName                (required) Git repository name

  --repoOwner=repoOwner              (required) Git repository owner

EXAMPLE
  $ sdlcpipelinehelper junit-report-publish --reportPaths="**/test-results/**/TEST-*.xml" --commit="$PULL_PULL_SHA"

See code: src/commands/junit-report-publish.ts

sdlcpipelinehelper sarif-publish

Convert SARIF report into markdown format and publish it as Quality Check

USAGE
  $ sdlcpipelinehelper sarif-publish

OPTIONS
  -h, --help                         show CLI help
  --appId=appId                      GitHub application id. Optionally use GH_APP_ID environment variable

  --checkConclusion=checkConclusion  Can be one of action_required, cancelled, failure, neutral, success, skipped,
                                     stale, or timed_out.
                                     When the conclusion is action_required, additional details should be
                                     provided on the site specified by details_url.

  --checkName=checkName              (required) check name

  --checkStatus=checkStatus          [default: completed] check status: queued, in_progress, or completed

  --commit=commit                    (required) commit SHA

  --detailsUrl=detailsUrl            Details URL about build. In our case link to Tekton dashboard.

  --installationId=installationId    GitHub application installationId. Optionally use GH_APP_INSTALLATION_ID
                                     environment variable

  --privateKey=privateKey            GitHub application primate key. Optionally use GH_APP_PRIVATE_KEY environment
                                     variable

  --repoName=repoName                (required) Git repository name

  --repoOwner=repoOwner              (required) Git repository owner

  --sourceRoot=sourceRoot            (required) sourceRoot DIR

See code: src/commands/sarif-publish.ts