Comparing version 0.0.1 to 2017.2.20
@@ -1,1 +0,1 @@ | ||
{"name":"busybox2","version":"0.0.1"} | ||
{"author":"kai zhu <kaizhu256@gmail.com>","bin":{"utility2":"lib.utility2.sh","utility2-github-crud":"lib.github_crud.js","utility2-istanbul":"lib.istanbul.js","utility2-jslint":"lib.jslint.js","utility2-uglifyjs":"lib.uglifyjs.js"},"description":"this zero-dependency package will run dynamic browser-tests with coverage (via electron and istanbul)","devDependencies":{"electron-lite":"kaizhu256/node-electron-lite#alpha"},"engines":{"node":">=4.0"},"homepage":"https://github.com/kaizhu256/node-utility2","keywords":["atom","atom-shell","browser","build","busybox","ci","code-coverage","continuous-integration","cover","coverage","docker","electron","headless","headless-browser","instrument","istanbul","jscover","jscoverage","phantom","phantomjs","slimer","slimerjs","test","travis","travis-ci","utility2","web"],"license":"MIT","main":"lib.utility2.js","name":"busybox2","nameAlias":"utility2","nameOriginal":"utility2","os":["darwin","linux"],"repository":{"type":"git","url":"https://github.com/kaizhu256/node-utility2.git"},"scripts":{"build-ci":"./lib.utility2.sh shRun shReadmeBuild","env":"env","example.sh":"./lib.utility2.sh shRunScreenCapture shReadmeTestSh example.sh","heroku-postbuild":"./lib.utility2.sh shRun shDeployHeroku","postinstall":"if [ -f lib.utility2.npm-scripts.sh ]; then ./lib.utility2.npm-scripts.sh postinstall; fi","publish-alias":"VERSION=$(npm info $npm_package_name version); for ALIAS in busybox busybox2 busyweb; do utility2 shRun shNpmPublish $ALIAS $VERSION; utility2 shRun shNpmTestPublished $ALIAS || exit $?; done","start":"export PORT=${PORT:-8080} && if [ -f assets.app.js ]; then node assets.app.js; return; fi && export npm_config_mode_auto_restart=1 && ./lib.utility2.sh shRun shIstanbulCover test.js","test":"export PORT=$(./lib.utility2.sh shServerPortRandom) && export PORT_REPL=$(./lib.utility2.sh shServerPortRandom) && export npm_config_mode_auto_restart=1 && ./lib.utility2.sh test test.js","test-all":"npm test --mode-coverage=all"},"version":"2017.2.20"} |
Install scripts
Supply chain riskInstall scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Network access
Supply chain riskThis module accesses the network.
Found 3 instances in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 1 instance in 1 package
Debug access
Supply chain riskUses debug, reflection and dynamic code execution features.
Found 3 instances in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 9 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Minified code
QualityThis package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.
Found 2 instances in 1 package
Empty package
Supply chain riskPackage does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Found 1 instance in 1 package
No README
QualityPackage does not have a README. This may indicate a failed publish or a low quality package.
Found 1 instance in 1 package
No contributors or author data
MaintenancePackage does not specify a list of contributors or an author in package.json.
Found 1 instance in 1 package
No License Found
License(Experimental) License information could not be found.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
No website
QualityPackage does not have a website.
Found 1 instance in 1 package
2207419
14
0
37449
2
1
875
1
3
1
87
33