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

threat-model-manager

v1.1.7

Published

Threat model documentation

Downloads

107

Readme

threat-model-manager

Documentation management for threat models

Building it

You can install from npm:

npm i threat-model-manager

Or build from source:

npm i
npm run build

If you build from source you will need to run:

node lib/cli.js generate filename.yaml

Running it

If installed from npm.

Currently there is only one command, generate:

threat-model-manager generate filename.yaml

Input file format

The input file is a YAML file of the following format:

classes:
  node-class-a:
    label: Class A
    threats:
    - type: <threat type>
      threat: text for threat
      notes: some text
      risk: a number
      ticket: a reference to a ticket for resolution/mitigation
components:
  component-a:
    label: Component A
nodes:
  node-name-a:
    label: The name for node a
    component: component-a
    classes:
    - node-class-a
    threats:
    - type: <threat type>
      threat: text for threat
      notes: some text
      risk: a number
      ticket: a reference to a ticket for resolution/mitigation
    flows:
    - to: node-name-b
      threats:
      - type: <threat type>
        threat: text for threat
        notes: some text
        risk: a number
        ticket: a reference to a ticket for resolution/mitigation

The threat types are one of:

  • spoofing
  • tampering
  • repudiation
  • information
  • denial
  • elevation

node names are only used for references between flows and nodes, but the model is checked to ensure there are no dangling references, but orphans are ok.

Output

The output is a graphviz dot file per component, and one overall, plus pngs for each.

Numeric references are generated on the fly, but are not stable if you add or remove nodes or flows.