statuses - npm Package Compare versions

Comparing version 1.2.0 to 1.2.1

codes.json

@@ -51,3 +51,3 @@ {
   "431": "Request Header Fields Too Large",
-  "451": "Unable For Legal Reasons",
+  "451": "Unavailable For Legal Reasons",
   "500": "Internal Server Error",
@@ -54,0 +54,0 @@ "501": "Not Implemented",

package.json

 {
   "name": "statuses",
   "description": "HTTP status utility",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "author": {
@@ -27,4 +27,3 @@ "name": "Jonathan Ong",
     "mocha": "1",
-    "request": "^2.44.0",
-    "stream-to-array": "^2.0.2"
+    "stream-to-array": "2"
   },
@@ -31,0 +30,0 @@ "scripts": {

README.md

@@ -22,4 +22,4 @@ # Statuses
 ```js
-status(403) // => 403
-status('403') // => 403
+status(403) // => 'Forbidden'
+status('403') // => 'Forbidden'
 status('forbidden') // => 403
@@ -26,0 +26,0 @@ status('Forbidden') // => 403

New alerts

New author

Supply chain risk

A 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

Improved metrics

Dev dependency count

4

decreased by-20%

Worsened metrics

Total package byte prevSize

8017

decreased by-0.12%

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes