Comparing version 0.0.0 to 1.0.0
{ | ||
"name": "premise", | ||
"version": "0.0.0", | ||
"description": "", | ||
"main": "index.js", | ||
"license": "MIT" | ||
"version": "1.0.0", | ||
"description": "Simple predicate logic chaining", | ||
"main": "premise.js", | ||
"dependencies": {}, | ||
"devDependencies": { | ||
"underscore": "^1.8.3" | ||
}, | ||
"scripts": { | ||
"test": "jasmine" | ||
}, | ||
"author": "", | ||
"license": "ISC" | ||
} |
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
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
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 v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
14634
6
319
1
1
65
1
2