Comparing version 0.1.2 to 0.1.3
{ | ||
"name": "nest", | ||
"version": "0.1.2", | ||
"version": "0.1.3", | ||
"description": "A Node HTTP client aimed at REST API's.", | ||
"repository": { | ||
"type": "git", | ||
"url": "http://github.com/votizen/nest.git" | ||
"url": "http://github.com/tim-smart/nest.git" | ||
}, | ||
"main": "./", | ||
"bugs": { | ||
"web": "http://github.com/votizen/nest/issues" | ||
"url": "http://github.com/tim-smart/nest/issues" | ||
}, | ||
@@ -18,4 +18,4 @@ "author": "Tim Smart <tim@fostle.com>", | ||
"engines": { | ||
"node": ">=0.4.0" | ||
"node": "0.6.x" | ||
} | ||
} |
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
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
No bug tracker
MaintenancePackage does not have a linked bug tracker in package.json.
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
Non-existent author
Supply chain riskThe package was published by an npm account that no longer exists.
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
Mixed license
License(Experimental) Package contains multiple licenses.
Found 1 instance in 1 package
No bug tracker
MaintenancePackage does not have a linked bug tracker in package.json.
Found 1 instance in 1 package
0
0
6942
5
206