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

@slauth.io/slauth

v1.5.2

Published

CLI that scans directories for usage of aws-sdk and generated IAM Policies

Downloads

48

Readme

Installation

npm install -g @slauth.io/slauth

Usage

  1. Set the OPENAI_API_KEY environment variable: export OPENAI_API_KEY=<key>
  2. Run slauth --help to see available commands

Commands

Scan

The scan command will look for any calls of your Cloud Provider sdk in your git repository and generate the necessary permissions for it.

slauth scan -p aws ../path/to/my/repository

Note: By default the scan command will print the result to stdout. Use -o,--output-file option to specify a file to output to.

Result:

The result of the scan command is an array of IAM Permissions.

Note: For aws cloud provider, if the resource is not explicit in the code (e.g. comes from a variable), we use a placholder for it. Before deploying the policies, you will have to manually change these placeholders with the correct resources the service will try to interact with.

Detected Policies:

[
  {
    "Version": "2012-10-17",
    "Id": "S3Policy",
    "Statement": [
      {
        "Sid": "S3Permissions",
        "Effect": "Allow",
        "Action": [
          "s3:PutObject",
          "s3:GetBucketAcl"
        ],
        "Resource": [
          "<S3_BUCKET_PLACEHOLDER>",
          "<S3_BUCKET_1_PLACEHOLDER>",
          "arn:aws:s3:::my_bucket_2/*"
        ]
      }
    ]
  },
  {
    "Version": "2012-10-17",
    "Id": "DynamoDBPolicy",
    "Statement": [
      {
        "Sid": "DynamoDBPermissions",
        "Effect": "Allow",
        "Action": [
          "dynamodb:PutItem"
        ],
        "Resource": [
          "<DYNAMODB_TABLE_PLACEHOLDER>"
        ]
      }
    ]
  },
  {
    "Version": "2012-10-17",
    "Id": "SQSPolicy",
    "Statement": [
      {
        "Sid": "SQSPermissions",
        "Effect": "Allow",
        "Action": [
          "sqs:SendMessage"
        ],
        "Resource": [
          "<SQS_QUEUE_URL_PLACEHOLDER>"
        ]
      }
    ]
  }
]
Available options
  • -p, --cloud-provider <cloudProvider> select the cloud provider you would like to generate policies for (choices: "aws", "gcp")
  • -m, --openai-model <openaiModel> select the openai model to use (choices: "gpt-3.5-turbo-16k", "gpt-4-32k")
  • -o, --output-file <outputFile> write generated policies to a file instead of stdout

Selecting which OpenAI Model to use

By default slauth will use gpt-4-32k as it provides the best results. You can still choose to use other models to scan you repo, specially if cost is a concern:

To choose a different model, use the -m option of the scan command

slauth scan -p aws -m gpt-3.5-turbo-16k ./path/to/my/repository

Available models:

  • gpt-3.5-turbo-16k (results with this model might be incomplete)
  • gpt-4-32k (default)

Example repos to test with

In case you want to give the CLI a quick test you can fork the following repositories.

Running in CI/CD

Slauth being a CLI, it can be easily integrated in your CI/CD pipelines.

Github Action Example

In this GitHub action workflow we install Slauth, run it and then output the result to an artifact which can then be downloaded so it can be used in your IaC.

name: scan
on:
  push:

permissions:
  contents: read

jobs:
  release:
    name: policy-scan
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - name: Setup Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 'lts/*'
      - name: Install Slauth
        run: npm install -g @slauth.io/slauth
      - name: Run Slauth
        env:
          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
        run: slauth scan -p aws -o ./policies.json .
      - name: Upload Artifact
        uses: actions/upload-artifact@v3
        with:
          name: policies
          path: policies.json

Development

  1. Set your OPENAI_API_KEY in the .env file at the root of the project
  2. Run npm i
  3. Install the slauth CLI globally: npm install -g .
  4. Compile tsc on file change: npm run build-watch
  5. Test it, slauth -h should work