Build graphviz from stack definition file. Outputs .dot file, .json file (structure), .md file (todo list), and .png or .svg graph. Companion to sst-serverless microservice stack

wintvelt

stack-graph

Error

Ignore

Warn

License

Maintenance

Miscellaneous

Quality

Supply chain risk

Vulnerability

Admins only

Organization members

Dashboard

<upgradeLink>Upgrade</upgradeLink> to access this feature

About

Blog

Socket CLI

Customers

Socket Dependency Search

Docs

Socket for GitHub

Love

Impersonation Mode Active

Update your browser to the latest version for the best experience.

Your web browser is outdated

Use another browser for the best experience.

Your web browser is unsupported

{{count, number}} commits last two months

{{count, number}} critical severity alert

{{count, number}} critical severity alerts

{{count, number}} dependency vulnerability

{{count, number}} dependency vulnerabilities

{{count, number}} development dependencies

{{count, number}} transitive dependencies

{{count, number}} version published last month

{{count, number}} versions published last month

{{count, number}} version published in last two months

{{count, number}} versions published in last two months

{{count, number}} version published last week

{{count, number}} versions published last week

{{count, number}} version published last year

{{count, number}} versions published last year

Socket undergoes annual SOC2 Type II audits. Socket customers can request a copy of the full SOC2 Type II report.

Allows organization owners and admins to access detailed records of actions taken by members of their organization, complete with timestamps.

Prevent compromised packages from infiltrating your supply chain by monitoring for changes in real-time.

Join our Discord community to get help from Socket engineers and other Socket users.

Compare millions of open source packages on socket.dev

Detect malicious code and risky behavior (e.g. network) in your dependencies using "deep package inspection"

All data is encrypted in transit and at rest using industry standard encryption algorithms.

Get a dedicated Socket account manager and access to Socket’s Customer Success team.

Get dedicated support from Socket engineers via email and Slack.

"Shift left" with the Socket Chrome extension and give intervene early, before developers choose risky or low quality dependencies.

Catch developers using risky dependencies and give them a "speed bump" to encourage good behavior

Install the Socket GitHub app to receive real-time dependency scanning and reports with every pull request.

Integrate Socket into your GitHub SCM to prevent risky dependencies from being installed.

Socket scans for vulnerabilities in your dependencies, including CVEs, security advisories, and more.

Socket supports dependencies in many languages, with most popular ecosystems coming in 2024. We've got you covered no matter what languages you use.

Enforce license policies across your organization

Receive a Microsoft Teams message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Get help migrating from Socket's free plan to Socket's paid plans.

Run Socket on-premises or in your own cloud environment.

Query for any dependency (at any version) across your entire organization

Integrate Socket into your CI/CD pipeline to prevent risky dependencies from being deployed to production.

Analyze an entire project to find supply chain risks

Tag projects to organize and filter your projects

Restrict access based on the roles of individual users within an organization.

Receive a Slack message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket is SOC2 Type II compliant and undergoes annual audits.

The Socket CLI allows teams to prevent risky dependencies from being installed, and to get dependency insights from the command line.

Socket supports SAML SSO for single sign-on and identity management.

Integrate Socket into your VS Code IDE to prevent risky dependencies from being installed.

Get a POST request anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket will analyzed your SBOMs up to a maximum number of dependencies.

API that allows you to analyze a project, lookup package scores and alerts, and more.

Create API tokens to authenticate with the Socket API and CLI.

The number of developers in your team. A developer is someone who made a commit to your organization's repositories scanned by Socket in the past month.

Use Socket to protect your private repositories.

Socket is always free for open source projects.

Socket retains all reporting data for 3 months, 1 year, or a custom term of your choice.

Access the threat feed that powers Socket.

Unlimited scale, self-hosting, and priority support for large teams.

For open-source projects, individuals, and small teams.

For growing teams with enhanced scale, security, and support.

There is a package with a similar name that is downloaded much more often.

There are packages with similar names that are downloaded much more often.

This may not be the package you want!

Instance

Alert Locations

Package

The {{ecosystem}} package {{- packageName}} receives a total of <strong>{{numWeeklyDownloadCount, number}}</strong> weekly downloads. As such, {{- packageName}} popularity was classified as <strong>{{popularity}}</strong>.

Is {{- packageName}} popular?

Is {{- packageName}} safe to use?

Is {{- packageName}} well maintained?

What is {{- packageName}}?

{{packageDescription}}Version: {{versionString}} was published by {{publisherName}}. Start using Socket to analyze {{- packageName}} and its {{dependencyCount, number}} dependencies to secure your app from supply chain attacks.

Sorry, it seems this package was removed from the registry

Package was removed

This package version has been unpublished, mostly likely due to security reasons

Package version was removed

Provide a detailed description of the malware...

Socket fights vulnerabilities and provides visibility, defense-in-depth, and proactive supply chain protection for JavaScript, Python, and Go dependencies.

Socket - Secure your dependencies. Ship with confidence.

Compare versions

{{- packageName}} - npm Package Compare versions

    - [ ] add function definition for `dbConsumer.js`

    - [ ] add permissions for `dbConsumer.js` to access `topic`

  - [ ] add queue stack for `cover-dlq-queue`

    - [ ] add function definition for `createUser.js`

    - [ ] add permissions for `createUser.js` to access `table`

    - [ ] add function definition for `cognitoSync.js`

    - [ ] add permissions for `cognitoSync.js` to access `verification-email`

    - [ ] add function definition for `preSignup.js`

    - [ ] add permissions for `preSignup.js` to access `getInvite.js` in `calm-invites` service

    - [ ] add function definition for `postAuth.js`

    - [ ] add permissions for `postAuth.js` to access `table`

    - [ ] add function definition for `updateUser.js`

    - [ ] add permissions for `updateUser.js` to access `table`

    - [ ] add function definition for `deleteUser.js`

    - [ ] add permissions for `deleteUser.js` to access `table`

    - [ ] add permissions for `deleteUser.js` to access `auth`

  - [ ] Manually setup email in AWS console for `verification-email`

    - [ ] add function definition for `updateCover.js`

    - [ ] add permissions for `updateCover.js` to access `table`

    - [ ] add permissions for `updateCover.js` to access `cover-dlq-queue`

    - [ ] add function definition for `get.js`

    - [ ] add permissions for `get.js` to access `table`

### In `/src` folder create the handler functions

    - [ ] add update for `table` to update cover

    - [ ] add update for `cover-dlq-queue` to failed cover calls

    - [ ] add update for `table` to create new user

  - [ ] create `updateUser.js` handler to change name (not cover)

    - [ ] add update for `table` to update user name

  - [ ] create `deleteUser.js` handler to deletes user

    - [ ] add update for `auth` to delete from cognito

  - [ ] create `cognitoSync.js` handler to Custom message

    - [ ] add update for `verification-email` to signup + forgot psw mails

  - [ ] create `preSignup.js` handler to Verify if invite exists

    - [ ] add query of `getInvite.js` in `calm-invites` service

  - [ ] create `postAuth.js` handler to update stats on visit

    - [ ] add update for `table` to update stats

  - [ ] create `dbConsumer.js` handler to db stream to publish changes

  - [ ] create `get.js` handler to user details upon login

### In `/npm` folder expose functions and arn info for client

  - [ ] expose arn for API `DELETE /user`

  - [ ] expose arn for function `getUser.js`

  - [ ] expose arn for function `getUserByEmail.js`

  - [ ] expose function `getUser.js`to query `get.js`

  - [ ] expose function `getUserByEmail.js`to query `getByEmail.js`

  - [ ] expose arn of `get.js` for permission to invoke function `getUser.js`

  - [ ] expose arn of `getByEmail.js` for permission to invoke function `getUserByEmail.js`

  - [ ] expose function `getUser.js` to query `get.js`

  - [ ] expose function `getUserByEmail.js` to query `getByEmail.js`

// libs to create checklist from structObj

// mark todo as done if already included as done in oldFile

const todoFrom = (oldFile) => (todo) => {

    const todoDone = todo.replace('[ ]', '[x]')

    const todoWasDone = oldFile.includes(`\n${todoDone}\n`)

    return (todoWasDone) ? todoDone : todo

// format name with maybe service name in it

        `\`${item.name}\` in \`${item.serviceName}\` service`

// add permission todos to a stack todolist

const addPermissionsForPubs = (todoList, node, indent = '') => {

    const { name, pubs = [], queries = [] } = node

    if (list.length === 0) return todoList

        const newTodo = `${indent}  - [ ] add permissions for \`${name}\` to access ${niceName(item)}`

const stackFromNode = (stacks, node) => {

    const noStackNeeded = (node.serviceName || node.type === "function")

    const nodeStack = output[node.name] || []

    const unsupported = ['email'].includes(node.type)

        `  - [ ] Manually setup ${node.type} in AWS console for \`${node.name}\``

        : `  - [ ] add ${node.type} stack for \`${node.name}\``

// add function def todo as stack or within other stack

const funcDefFromNode = (stacks, node) => {

    const isInternalFunc = (node.type === 'function' && !node.serviceName)

    const isLambda = (!node.cluster === 'input') // input funcs are generated in npm client package

    const needsStack = (!node.subs || node.subs.length === 0)

        const nodeStack = [`  - [ ] add function stack for \`${node.name}\``]

        output[node.name] = addPermissionsForPubs(output[node.name], node, '  ')

    const funcOwner = node.subs && node.subs[0].name

    const ownerNotInStack = !funcOwner || !output[funcOwner]

    const newTodo = `    - [ ] add function definition for \`${node.name}\``

    output[funcOwner] = addPermissionsForPubs(output[funcOwner], node, '  ')

const addLinesForPubs = (todoList, node) => {

    const { pubs = [], queries = [] } = node

        const desc = (query.description) ? ` to ${query.description}` : ''

        const newTodo = `    - [ ] add query of ${niceName(query)}${desc}`

        const desc = (pub.description) ? ` to ${pub.description}` : ''

        const newTodo = `    - [ ] add update for ${niceName(pub)}${desc}`

const handlerFromFuncNode = (srcs, node) => {

    const desc = (node.description) ? ` to ${node.description}` : ''

    output[node.name] = [`  - [ ] create \`${node.name}\` handler${desc}`]

    output[node.name] = addLinesForPubs(output[node.name], node)

// add todos to expose stuff in npm client

const clientTodosFromNode = (clientLines, node) => {

            const arnName = (node.pubs) ?

                `to invoke \`${node.pubs[0].name}\``

                ` to invoke \`${node.pubs[0].name}\``

                    `to query \`${node.queries[0].name}\``

                    ` to query \`${node.queries[0].name}\``

		@@ -111,9 +111,14 @@ // libs to create checklist from structObj
		case "function":
		const arnName = (node.pubs) ?
		node.pubs[0].name
		: (node.queries) ?
		node.queries[0].name
		: ' (something?)'
		const specs = (node.pubs) ?
		`to invoke \`${node.pubs[0].name}\``
		` to invoke \`${node.pubs[0].name}\``
		: (node.queries) ?
		`to query \`${node.queries[0].name}\``
		: ''
		` to query \`${node.queries[0].name}\``
		: ' (something?)'
		output.push(` - [ ] expose function \`${node.name}\`${specs}`)
		output.push(` - [ ] expose arn for function \`${node.name}\``)
		output.push(` - [ ] expose arn of \`${arnName}\` for permission to invoke function \`${node.name}\``)
		break
		@@ -120,0 +125,0 @@

		{
		"name": "stack-graph",
		"version": "1.6.0",
		"version": "1.7.0",
		"description": "Build graphviz from stack definition file. Outputs .dot file, .json file (structure), .md file (todo list), and .png or .svg graph. Companion to sst-serverless microservice stack",
		@@ -5,0 +5,0 @@ "main": "local.js",

		@@ -61,5 +61,5 @@ ## Todo list to create your stack
		- [ ] expose arn for API `POST /user`
		- [ ] expose arn for function `getUser.js`
		- [ ] expose arn for function `getUserByEmail.js`
		- [ ] expose function `getUser.js`to query `get.js`
		- [ ] expose function `getUserByEmail.js`to query `getByEmail.js`
		- [ ] expose arn of `get.js` for permission to invoke function `getUser.js`
		- [ ] expose arn of `getByEmail.js` for permission to invoke function `getUserByEmail.js`
		- [ ] expose function `getUser.js` to query `get.js`
		- [ ] expose function `getUserByEmail.js` to query `getByEmail.js`

Improved metrics