@lskjs/billing - npm Package Compare versions

Comparing version 3.16.4 to 3.16.5

package.json

 {
   "name": "@lskjs/billing",
-  "version": "3.16.4",
+  "version": "3.16.5",
   "description": "LSK.js module for adding billing in cabinet",
   "author": "Igor Suvorov <[e-mail]> (https://github.com/isuvorov)",
-  "private": false,
   "dependencies": {
@@ -12,11 +11,2 @@ "@lskjs/err": "2.85.1",
   },
-  "devDependencies": {
-    "@lskjs/db": "^3.16.4",
-    "@lskjs/server-api": "^3.16.4",
-    "axios": "0.21.2",
-    "bluebird": "3.7.2",
-    "crypto-js": "4.1.1",
-    "lodash": "4.17.21",
-    "yandex-checkout": "1.0.13"
-  },
   "peerDependencies": {
@@ -30,10 +20,2 @@ "@lskjs/db": "2.x",
   },
-  "//": "///////////========================/////////========================/////////========================//////////",
-  "prettier": "@lskjs/eslint-config/prettier",
-  "eslintConfig": {
-    "extends": "@lskjs/eslint-config/nostrict"
-  },
-  "jest": {
-    "preset": "@lskjs/jest-config"
-  },
   "files": [
@@ -56,3 +38,2 @@ "lib"
   },
-  "///": "//////////========================/////////========================/////////========================/////////",
   "repository": "https://github.com/lskjs/lskjs/tree/master//libs-core/billing",
@@ -78,3 +59,2 @@ "homepage": "https://github.com/lskjs/lskjs/tree/master//libs-core/billing",
   ],
-  "////": "/////////========================/////////========================/////////========================/////////",
   "optionalDeps": {
@@ -84,8 +64,3 @@ "yandex-checkout": "*",
   },
-  "scripts": {
-    "dev": "            lsk run dev",
-    "build": "          lsk run build",
-    "test": "           lsk run test",
-    "release": "        lsk run release"
-  }
-}
+  "gitHead": "77a0fb26661eb4464eef5bc379f6cd72d42c3261"
+}

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

No README

Quality

Package does not have a README. This may indicate a failed publish or a low quality package.

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

Dev dependency count

0

decreased by-100%

Worsened metrics

Total package byte prevSize

198719

decreased by-2.65%

Number of package files

45

decreased by-4.26%

Number of low quality alerts

1

increased byInfinity%

Number of medium quality alerts

2

increased by100%

Number of lines in readme file

0

decreased by-100%

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes