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

@securityscorecard/experimental-action-app

v1.0.0

Published

experimental action app

Downloads

3

Readme

Experimental

Action app

IMPORTANT DISCLAIMER: this is still in an experimental phase, please do not use this in a real SecurityScorecard app yet.

Action Action app used to demostrate the workflow of SecurityScorecard's Marketplace.

One of the ways apps can extend our platform is by registering additional actions that can be invoked in Rules.

Getting Started

1.- Create a SecurityScorecard API Token. Select Generate new API token (copy the result)

2.- Configure your CLI token

ssc config

during the process specify wich enviroment you want to set

3.- Initialize your project

ssc init -e experimental-action-app

4.- Modify the manifest at /public/manifest.json with your details

If you are not familiar with the manifest, you should also check the experimental-bare-app example that already explains the basics

{
  ...
  "actions": [
    {
      // unique identifier for this action (must be snake_case)
      "id": "notify_channel",
      // human-readable description of this action
      "name": "Notify Channel",
      // the url in your app that will be called (POST) to execute this action
      // note: as other urls, this can be relative to the manifest url
      "url": "actions/notify_channel",
      // optional, url to call (POST) for settings to show in the rule builder
      "settings_url": "actions/notify_channel/settings",
      // optional, instead of the above, when settings are fixed (independent of user)
      "settings": {
        // example field to show in the rule builder (will be shown as dropdown)
        "department": {
          "options": [{
            "key": "it",
            "value": "IT"
          }, {
            "key": "sec-ops",
            "value": "SecOps"
          }]
        }
      }
    }
  ]
}

5.- Deploy your app

  • use already provided example with Vercel (vercel.json) or any cloud provider you like.

6.- Install your app

Inside your projects manifest route (ex. /public/manifest)

ssc install -e development

the CLI will display the URL where your project is, but you could also find it throug SecurityScorecard > Marketplace > (filter) Installed Apps

7.- Create a new Rule

Navigate to SecurityScorecard > My Settings > Rules. Then, select + Create my own rule.

The ui display three dropdowns, each one refers to a property that the rule builder will take into consideration, event, for and action. To use our app we need to provide a new rule setting the action dropdown to use our new event Notify Channel (ref.: manifest.json > name).

8.- Execute the action

Now all the events triggering the condition we set on our rule will call our action url (ref.: manifest.json > url).