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 🙏

© 2024 – Pkg Stats / Ryan Hefner

bugcatcher-github-action

v0.1.0

Published

Faster Than Light Static Analysis and GitHub Continuous Integration

Downloads

5

Readme

Faster Than Light BugCatcher GitHub Action

Use this GitHub Action to add the Faster Than Light BugCatcher static analysis tool to your CI/CD workflow. Configure your Action with your tolerance (severity threshold) for the severity level of issues which will trigger a failure in your workflow.

Inputs

GITHUB_TOKEN

Required : This token is included in the secrets dictionary passed to the GitHub workflow and must be passed through to the Action in order to allow it access to the contents of some repositories. This is simply done by adding a with parameter in your yaml file (as shown below).

BUGCATCHER_TOKEN

Required : A security identifier token copied from your BugCatcher account.

Note: This token must be saved to your GitHub repository's  Settings > Secrets  collection as BUGCATCHER_TOKEN.

SEVERITY_THRESHOLD

options: (high, medium, low)

Optional : The minimum severity level you want to trigger a failure in your testing workingflow. If no value is specified, your checks will pass and include a link to the BugCatcher test results.

Outputs

results

A list of results from BugCatcher static analysis testing.

Example usage

Add file: .github/workflows/bugcatcher.yml :

name: BugCatcher

on: [push]

jobs:
  CI:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1
      - name: Use Node.js 12
        uses: actions/setup-node@v1
        with:
          node-version: 12
      - name: BugCatcher Static Analysis
        uses: faster-than-light/github-action@master
        with:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          BUGCATCHER_TOKEN: ${{ secrets.BUGCATCHER_TOKEN }}
          SEVERITY_THRESHOLD: high