Comparing version 0.0.0 to 0.1.14
{ | ||
"name": "node", | ||
"version": "0.0.0" | ||
} | ||
"version": "0.1.14", | ||
"description": "node", | ||
"main": "index.js", | ||
"keywords": [ | ||
"runtime" | ||
], | ||
"scripts": { | ||
"preinstall": "node installArchSpecificPackage" | ||
}, | ||
"bin": { | ||
"node": "bin/node" | ||
}, | ||
"dependencies": { | ||
"node-bin-setup": "^1.0.0" | ||
}, | ||
"license": "ISC", | ||
"author": "", | ||
"engines": { | ||
"npm": ">=5.0.0" | ||
} | ||
} |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
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
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Deprecated
MaintenanceThe maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
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
985
3
0
0
0
18
1
1
2
+ Addednode-bin-setup@^1.0.0
+ Addednode-bin-setup@1.1.3(transitive)