color-contrast-checker - npm Package Compare versions

Comparing version 1.2.0 to 1.3.0

package.json

 {
   "name": "color-contrast-checker",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "This is an accessibility validator based on WCAG 2.0 standard for checking the color contrast.",
@@ -13,3 +13,3 @@ "main": "src/color-contrast-checker.js",
   "scripts": {
-    "test": "echo \"Error: no test specified\" && exit 1"
+    "test": "mocha --reporter spec"
   },
@@ -59,3 +59,7 @@ "repository": {
   ],
-  "_resolved": "http://registry.npmjs.org/color-contrast-checker/-/color-contrast-checker-1.2.0.tgz"
+  "_resolved": "http://registry.npmjs.org/color-contrast-checker/-/color-contrast-checker-1.2.0.tgz",
+  "devDependencies": {
+    "chai": "^4.1.0",
+    "mocha": "^3.4.2"
+  }
 }

README.md

@@ -5,4 +5,7 @@ # Color Contast Checker
 
-The formula (L1/L2) for contrast is based on [ISO-9241-3] and [ANSI-HFES-100-1988] standards as described here : http://www.w3.org/TR/2008/REC-WCAG20-20081211/#relativeluminancedef
+The formula (L1/L2) for contrast is based on [ISO-9241-3] and [ANSI-HFES-100-1988] standards as described here : 
 
+http://www.w3.org/TR/2008/REC-WCAG20-20081211/#relativeluminancedef
+http://www.w3.org/TR/WCAG20/#contrast-ratiodef
+
 Installation:
@@ -120,2 +123,8 @@ ------------
 
-Its sweet and simple completely based on http://www.w3.org/TR/WCAG20/#contrast-ratiodef.
+## Tests
+
+  `npm test`
+
+## Contributing
+
+In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.

New alerts

License Policy Violation

License

This 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 risk

Package 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

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Uses eval

Supply chain risk

Package 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

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Minified code

Quality

This 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 1 instance in 1 package

No tests

Quality

Package does not have any tests. This is a strong signal of a poorly maintained or low quality package.

Found 1 instance in 1 package

Improved metrics

Number of low quality alerts

0

decreased by-100%

Number of lines in readme file

129

increased by7.5%

Number of low supply chain risk alerts

0

decreased by-100%

Worsened metrics

Total package byte prevSize

16011

decreased by-87.17%

Dev dependency count

2

increased byInfinity%

Number of package files

7

decreased by-61.11%

Lines of code

257

decreased by-89.28%

No dependency changes