Gathering detailed insights and metrics for sandbox-debugger-server
Gathering detailed insights and metrics for sandbox-debugger-server
Installations
npm install sandbox-debugger-serverDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
20.9.0
NPM Version
10.1.0
Score
57.2
Supply Chain
90
Quality
74.3
Maintenance
50
Vulnerability
99.3
License
Releases
Unable to fetch releases
Languages
2
JavaScript
Dockerfile
JavaScript (98.3%)
Dockerfile (1.7%)
Developer
jameskyburz
Download Statistics
Total Downloads
13,524
Last Day
2
Last Week
3
Last Month
126
Last Year
1,551
GitHub Statistics
11 Stars
299 Commits
1 Watchers
6 Branches
1 Contributors
Updated on Nov 21, 2024
Bundle Size
362.61 kB
Minified
185.41 kB
Minified + Gzipped
Maintainers
1
Package Meta Information
Latest Version
0.2.45
Package Id
sandbox-debugger-server@0.2.45
Unpacked Size
8.99 kB
Size
3.25 kB
File Count
3
NPM Version
10.1.0
Node Version
20.9.0
Published on
Dec 08, 2023
Total Downloads
Cumulative downloads
Total Downloads
13,524
Last Day
0%
2
Compared to previous day
Last Week
-97.2%
3
Compared to previous week
Last Month
10.5%
126
Compared to previous month
Last Year
22%
1,551
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
4
🐛 sandbox-debugger 🐛
Debug a Node.js process anywhere using chrome://inspect or node-inspect
| node debug port 9229 | ⟷ | sandbox debug client | ⟷ | sandbox debug broker |
|---|
Interactive debugging using inspect, debug the same way you do with a local process.
Supports a Node.js process running
- on a machine you can't ssh / don't have access to
- in a Docker Container with no exposed ports
- on Travis CI
- on Github Actions
- on Bitbucket Pipelines
- on GitLab CI/CD
- on AWS CodeBuild
- on AWS Lambda
- on Heroku
- on Runkit
- anywhere that allows outbound internet traffic to port 80
How it works?
Node opens a websocket when in debug mode, both the sandbox server and client work by piping the websocket data via the broker.
Run sandbox server
The server is used as a gatekeeper for the debug messages.
1npx sandbox-debugger-server
or
1ᐅ docker run \ 2 --name sandbox-debugger \ 3 -ti \ 4 --rm \ 5 -p 9229:9229 \ 6 jameskyburz/sandbox-debugger
The server will output
1 Debug server started! 2 3 - To debug a new process: 4 export DEBUG_PROXY=xxx.xxx.x.xxx:9229 5 node index.js 6 7 - To debug an existing process: 8 export DEBUG_PROXY=xxx.xxx.x.xxx:9229 9 export DEBUG_PID=<pid of node process> 10 npx sandbox-debugger 11 12 - Find pid of first running Node.js process 13 ps ax | 14 grep 'no[d]e ' | 15 awk '{print $1}' | 16 head -n 1 17 18 - Allow remote access to me: 19 npx ngrok http 9229 --scheme http
Create a tunnel to our sandbox server process
Using ngrok you can tunnel to the locally running broker from for example aws lambda.
1npx ngrok http 9229 --scheme http
Client
Example debug current process
1// index.js 2require('sandbox-debugger') 3debugger 4console.log('all done')
1# DEBUG_PROXY is ip:port to sandbox broker 2DEBUG_PROXY=ip:port node index.js
Example debug an already running process
1# DEBUG_PROXY is ip:port to sandbox broker 2# DEBUG_PID is pid of process to debug 3DEBUG_PROXY=ip:port DEBUG_PID=x npx sandbox-debugger
AWS Lambda
Environment variable DEBUG_PROXY needs to point to the ngrok address including the port part :80.
The easiest way to debug lambda is to edit the code in aws console.
Copy the contents of https://unpkg.com/sandbox-debugger@latest/dist/index.js to debug.js, and require('./debug.cjs') instead of sandbox-debugger
ESM example
1 import { createRequire } from 'node:module' 2 const require = createRequire(import.meta.url) 3 require('./debug.cjs')
license
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
Found 0/6 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/dependabot.yml:1
- Warn: no topLevel permission defined: .github/workflows/dockerimage.yml:1
- Info: no jobLevel write permissions found
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/dependabot.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/JamesKyburz/sandbox-debugger/dependabot.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/dependabot.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/JamesKyburz/sandbox-debugger/dependabot.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/dependabot.yml:35: update your workflow using https://app.stepsecurity.io/secureworkflow/JamesKyburz/sandbox-debugger/dependabot.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/dockerimage.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/JamesKyburz/sandbox-debugger/dockerimage.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/dockerimage.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/JamesKyburz/sandbox-debugger/dockerimage.yml/main?enable=pin
- Warn: containerImage not pinned by hash: packages/server/Dockerfile:1: pin your Docker image by updating node:lts-alpine3.13 to node:lts-alpine3.13@sha256:c7f8af31c7c4bb2221da18b67ccbe6d0632dab86d015573857b5a91afbedcf8c
- Warn: npmCommand not pinned by hash: packages/server/Dockerfile:10
- Warn: npmCommand not pinned by hash: packages/server/Dockerfile:11
- Info: 0 out of 4 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
- Info: 0 out of 1 containerImage dependencies pinned
- Info: 0 out of 2 npmCommand dependencies pinned
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 24 are checked with a SAST tool
Reason
13 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-r683-j2x4-v87g
- Warn: Project is vulnerable to: GHSA-rxrc-rgv4-jpvx
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
Score
2.4
/10
Last Scanned on 2025-06-30
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More