dir-parser - npm Package Compare versions

Comparing version 1.1.6 to 1.1.7

dir-info.txt

@@ -1,40 +0,15 @@
-dir-parser ( Directorys: 8, Files: 31 )
- +-- bin
- ¦   +-- parser.js
- +-- node_modules
- ¦   +-- commander
- ¦   ¦   +-- typings
- ¦   ¦   ¦   +-- index.d.ts
- ¦   ¦   +-- CHANGELOG.md
- ¦   ¦   +-- index.js
- ¦   ¦   +-- LICENSE
- ¦   ¦   +-- package.json
- ¦   ¦   +-- Readme.md
- ¦   +-- funclib
- ¦   ¦   +-- funclib.core.js
- ¦   ¦   +-- funclib.js
- ¦   ¦   +-- funclib.min.js
- ¦   ¦   +-- index.d.ts
- ¦   ¦   +-- index.js
- ¦   ¦   +-- package.json
- ¦   ¦   +-- README.md
- ¦   +-- progress
- ¦       +-- lib
- ¦       ¦   +-- node-progress.js
- ¦       +-- CHANGELOG.md
- ¦       +-- index.js
- ¦       +-- LICENSE
- ¦       +-- Makefile
- ¦       +-- package.json
- ¦       +-- Readme.md
- +-- src
- ¦   +-- base.js
- ¦   +-- dir-parser.js
- +-- .gitignore
- +-- dir-parser.png
- +-- index.js
- +-- package-lock.json
- +-- package.json
- +-- parser.conf.json
- +-- README.md
- +-- test.js
+dir-parser ( directories: 2, Files: 12 )
+ ├─ bin
+ │ └─ parser.js
+ ├─ src
+ │ ├─ base.js
+ │ └─ dir-parser.js
+ ├─ .gitignore
+ ├─ dir-parser.png
+ ├─ index.d.ts
+ ├─ index.js
+ ├─ package-lock.json
+ ├─ package.json
+ ├─ parser.conf.json
+ ├─ README.md
+ └─ test.js

package.json

 {
   "name": "dir-parser",
-  "version": "1.1.6",
+  "version": "1.1.7",
   "description": "Parse a directory and generate it's structure tree.",
@@ -5,0 +5,0 @@ "main": "index.js",

README.md

@@ -127,4 +127,5 @@ # Dir Parser
 ### Use dir-parser in javaScript code
+Interfaces
 ```
-parser(dirPath: string, ptions: Options): Promise<Parsed>
+parser(dirPath: string, options: Options): Promise<Parsed>
 
@@ -131,0 +132,0 @@ interface Options {

New alerts

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

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

Found 1 instance in 1 package

Fixed alerts

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

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

Found 1 instance in 1 package

Improved metrics

Number of lines in readme file

569

0.18%

Worsened metrics

Total package byte prevSize

119807

-0.6%

No dependency changes