Gathering detailed insights and metrics for npm-package-user-scripts-gui
Gathering detailed insights and metrics for npm-package-user-scripts-gui
Gathering detailed insights and metrics for npm-package-user-scripts-gui
Gathering detailed insights and metrics for npm-package-user-scripts-gui
npm install npm-package-user-scripts-gui
Typescript
Module System
Node Version
NPM Version
50.7
Supply Chain
76.6
Quality
66.2
Maintenance
50
Vulnerability
95.8
License
JavaScript (88.48%)
Shell (9.67%)
Visual Basic (0.69%)
Vim Script (0.61%)
Batchfile (0.55%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
1 Stars
34 Commits
1 Forks
2 Watchers
1 Branches
1 Contributors
Updated on Mar 16, 2025
Latest Version
0.0.8
Package Id
npm-package-user-scripts-gui@0.0.8
Unpacked Size
59.62 kB
Size
40.62 kB
File Count
23
NPM Version
6.4.1
Node Version
10.13.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
1
GUI interface to npm-package-user-scripts-list
command.
The idea of this tool came to my mind when I tried to introduce my son to the development of node projects and manage them using npm scripts from the console.
This script scans current project (in running path) package.json
commands (see
npm-package-user-scripts-list
for parsing details) and shows minimalistic window for interactive running your
service tasks.
Take in mind that the content of the log tab is updated only after the command is completed. All logs are doubled on stdout.
It may be preferable to install the package globally because each local
installation recompiles its own libui
library instance.
See LibUI-Node Requirements -- used interface engine (required some build tools for compiling sources).
For current project:
1$ npm i -S npm-package-user-scripts-gui
Global:
1$ npm i -g npm-package-user-scripts-gui
In js code:
1const ScriptCommandsGUI = require('./');
2
3const commandsWindow = new ScriptCommandsGUI({
4
5 // See options reference below...
6
7 /** Datetime format */
8 dateformat: 'yyyy.mm.dd, HH:MM:ss',
9
10 /** Minimal window width */
11 width: 800,
12
13});
14
15commandsWindow.showWindow();
Linux/MacOS shell command line:
1$ npm-package-user-scripts-gui &
Windows shell command line (console window will be opened, minimized and closed after program finish):
1$ start /min npm run -s cmd-gui ^& exit
Another convenient way to run the program on Windows is with vbasic script like this:
1CreateObject("Wscript.Shell").Run "npm run -s cmd-gui", 0
(Thanks to Kees Bakker, see his article How to start Node.js app windowless in Windows - KeesTalksTech.)
See also scripts npm-launcher.cmd
, npm-launcher.sh
, npm-launcher.vbs
(included in package) for global-installed package launch.
All options are optional. :)
child_process.exec
); @see child_process.exec (default: {}
)'yyyy.mm.dd HH:MM:ss'
)600
)200
)package.json
's name
field) (default: 'Commands'
){ test: { title: 'Test' } }
)' '
)Initial screen:
Running command:
Successfully finished command:
Log tab:
Failed command:
Show error in the log tab:
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 0/30 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 SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
30 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
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