modulejs - npm Package Compare versions
Comparing version 0.0.1 to 2.0.1
| { | ||
| "name": "modulejs", | ||
| "description": "browser side module manager.", | ||
| "version": "0.0.1", | ||
| "author": "Devrim Yasar <devrim@koding.com>", | ||
| "contributors": [ | ||
| { | ||
| "name": "Chris Thorn", | ||
| "email": "chris@koding.com" | ||
| } | ||
| ], | ||
| "keywords": [ | ||
| "require", | ||
| "requirejs" | ||
| ], | ||
| "repository": "git://github.com/koding/modulejs", | ||
| "main": "index", | ||
| "engines": { | ||
| "node": ">= 0.2.9 < 0.7.0" | ||
| "version": "2.0.1", | ||
| "description": "Lightweight JavaScript module system.", | ||
| "homepage": "https://larsjung.de/modulejs/", | ||
| "bugs": "https://github.com/lrsjng/modulejs/issues", | ||
| "author": "Lars Jung <lrsjng@gmail.com> (https://larsjung.de)", | ||
| "license": "MIT", | ||
| "repository": { | ||
| "type": "git", | ||
| "url": "https://github.com/lrsjng/modulejs.git" | ||
| }, | ||
| "subdomain": "modulejs", | ||
| "main": "dist/modulejs.js", | ||
| "scripts": { | ||
| "start": "index.js" | ||
| "lint": "eslint .", | ||
| "test": "node test", | ||
| "check": "npm run -s lint && npm run -s test", | ||
| "cover": "isparta cover --dir coverage --report text --report html test", | ||
| "build": "node ghu release", | ||
| "precommit": "npm run -s check && npm run -s build" | ||
| }, | ||
| "devDependencies": { | ||
| "babel-loader": "6.2.4", | ||
| "babel-preset-es2015": "6.9.0", | ||
| "eslint": "3.1.1", | ||
| "ghu": "0.7.0", | ||
| "isparta": "4.0.0", | ||
| "scar": "0.14.0" | ||
| }, | ||
| "engines": { | ||
| "node": ">=6.0.0" | ||
| } | ||
| } | ||
| } |
New alerts
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
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
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Fixed alerts
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
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 bug tracker
MaintenancePackage does not have a linked bug tracker 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
Improved metrics
- Total package byte prevSize
- increased by8567.86%
46113
- Number of package files
- increased by866.67%
29
- Number of low license alerts
- decreased by-100%
0
- Lines of code
- increased byInfinity%
1052
- Number of low quality alerts
- decreased by-50%
1
- Number of lines in readme file
- increased by4800%
49
Worsened metrics
- Dev dependency count
- increased byInfinity%
6
- Number of low supply chain risk alerts
- increased by100%
2
- Number of medium supply chain risk alerts
- increased by100%
2